When a ConverseCommand or ConverseStreamCommand request includes a
`toolConfig.tools` array, map each `toolSpec` to LLMObs'
`{ name, description, schema }` shape and attach it to the span via
the new `tagToolDefinitions` API (see parent PR #8082).

- utils.js: new `extractConverseToolDefinitions` helper.
- llmobs/plugins/bedrockruntime.js: call it on Converse requests.
- spec: assert on the `toolDefinitions` round-trip.

Brings Node parity with dd-trace-py's Bedrock Converse integration
for the "Available Tools" UI section.

Ref: MLOB-3509

…sent

`tagToolDefinitions` now logs a failure for non-array / empty input
(see #8082). The Bedrock plugin previously called it unconditionally
on every Converse request — `extractConverseToolDefinitions` returns
`[]` when there's no `toolConfig`, which would now produce noisy
`invalid_tool_definitions` logs on every tool-less Converse call.
Gate the call on `length > 0`.

When a ConverseCommand or ConverseStreamCommand request includes a
`toolConfig.tools` array, map each `toolSpec` to LLMObs'
`{ name, description, schema }` shape and attach it to the span via
the new `tagToolDefinitions` API (see parent PR #8082).

- utils.js: new `extractConverseToolDefinitions` helper.
- llmobs/plugins/bedrockruntime.js: call it on Converse requests.
- spec: assert on the `toolDefinitions` round-trip.

Brings Node parity with dd-trace-py's Bedrock Converse integration
for the "Available Tools" UI section.

Ref: MLOB-3509

…sent

`tagToolDefinitions` now logs a failure for non-array / empty input
(see #8082). The Bedrock plugin previously called it unconditionally
on every Converse request — `extractConverseToolDefinitions` returns
`[]` when there's no `toolConfig`, which would now produce noisy
`invalid_tool_definitions` logs on every tool-less Converse call.
Gate the call on `length > 0`.

When a ConverseCommand or ConverseStreamCommand request includes a
`toolConfig.tools` array, map each `toolSpec` to LLMObs'
`{ name, description, schema }` shape and attach it to the span via
the new `tagToolDefinitions` API (see parent PR #8082).

- utils.js: new `extractConverseToolDefinitions` helper.
- llmobs/plugins/bedrockruntime.js: call it on Converse requests.
- spec: assert on the `toolDefinitions` round-trip.

Brings Node parity with dd-trace-py's Bedrock Converse integration
for the "Available Tools" UI section.

Ref: MLOB-3509

…sent

`tagToolDefinitions` now logs a failure for non-array / empty input
(see #8082). The Bedrock plugin previously called it unconditionally
on every Converse request — `extractConverseToolDefinitions` returns
`[]` when there's no `toolConfig`, which would now produce noisy
`invalid_tool_definitions` logs on every tool-less Converse call.
Gate the call on `length > 0`.

When a ConverseCommand or ConverseStreamCommand request includes a
`toolConfig.tools` array, map each `toolSpec` to LLMObs'
`{ name, description, schema }` shape and attach it to the span via
the new `tagToolDefinitions` API (see parent PR #8082).

- utils.js: new `extractConverseToolDefinitions` helper.
- llmobs/plugins/bedrockruntime.js: call it on Converse requests.
- spec: assert on the `toolDefinitions` round-trip.

Brings Node parity with dd-trace-py's Bedrock Converse integration
for the "Available Tools" UI section.

Ref: MLOB-3509

…sent

`tagToolDefinitions` now logs a failure for non-array / empty input
(see #8082). The Bedrock plugin previously called it unconditionally
on every Converse request — `extractConverseToolDefinitions` returns
`[]` when there's no `toolConfig`, which would now produce noisy
`invalid_tool_definitions` logs on every tool-less Converse call.
Gate the call on `length > 0`.

When a ConverseCommand or ConverseStreamCommand request includes a
`toolConfig.tools` array, map each `toolSpec` to LLMObs'
`{ name, description, schema }` shape and attach it to the span via
the new `tagToolDefinitions` API (see parent PR #8082).

- utils.js: new `extractConverseToolDefinitions` helper.
- llmobs/plugins/bedrockruntime.js: call it on Converse requests.
- spec: assert on the `toolDefinitions` round-trip.

Brings Node parity with dd-trace-py's Bedrock Converse integration
for the "Available Tools" UI section.

Ref: MLOB-3509

…sent

`tagToolDefinitions` now logs a failure for non-array / empty input
(see #8082). The Bedrock plugin previously called it unconditionally
on every Converse request — `extractConverseToolDefinitions` returns
`[]` when there's no `toolConfig`, which would now produce noisy
`invalid_tool_definitions` logs on every tool-less Converse call.
Gate the call on `length > 0`.

* feat(llmobs): add tool_definitions support to Tagger

Introduces `_ml_obs.meta.tool_definitions` for LLM spans, mirroring the
shape already produced by dd-trace-py. Each definition is
`{ name, description, schema }`.

- `constants/tags.js`: new `TOOL_DEFINITIONS` tag key.
- `tagger.js`: new `tagToolDefinitions(span, toolDefinitions)` that
  validates entries and stores them in the registry. Matches the
  `#filterToolCalls` validation style.
- `span_processor.js`: forwards the registry entry to
  `meta.tool_definitions` on LLM spans.
- `test/llmobs/util.js`: assertion support for a new
  `toolDefinitions` expected field.

No integration plugin emits tool definitions yet; this unblocks
Bedrock Converse (see follow-up PR) and opens the door for
parity follow-ups on openai/anthropic/langchain/ai-sdk.

* fix(llmobs): sanitize tool_definitions through serialization guard

Route `tool_definitions` through `#addObject` before assigning to
`meta`, matching the existing `metadata` path. Direct assignment
bypassed the circular-ref / BigInt substitution done via
`UNSERIALIZABLE_VALUE_TEXT`, so a user-provided schema with a cycle
or unserializable value would make `JSON.stringify(event)` throw in
the span writer and the whole LLMObs span would get dropped.

This is a generic-infra safety fix: the current Bedrock caller is
safe by construction (the AWS SDK JSON.stringifies the request
before send), but `tagToolDefinitions` is meant to be reused by
other plugins and eventually the public `llmobs.annotate()` surface
where the upstream-already-serialized guarantee doesn't hold.

* fix(llmobs): handleFailure in tagToolDefinitions for malformed input

Add an `else` branch that calls `#handleFailure` for non-array /
empty input. Matches the validation pattern used by other tagger
methods. Flagged on review.

* test(llmobs): cover tagToolDefinitions happy path and malformed input

Adds a `tagToolDefinitions` describe block in the tagger spec mirroring
the `tagMetrics` style: one happy-path test asserting the tag is set,
and one negative test asserting the malformed-input branch (non-array,
empty array, undefined) routes through `#handleFailure`.

* test(llmobs): cover tool_definitions sanitization in span processor

* test(llmobs): clarify intent of nested cycle in tool_definitions test

* test(llmobs): simplify tool_definitions test to forwarding only