get_stream_info

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It usefully discloses that probe=True performs an 'active' query that fetches codecs, SDP, and byte counters, implying a heavier and possibly side-effecting call than a passive read. It says nothing about permissions, cost/latency of probing, or whether the call is safe/non-mutating.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core purpose front-loaded and the optional behavior immediately after. No filler or restatement of the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, and both parameters are accounted for. The remaining gap is the unresolved relationship to probe_stream, which matters given that sibling's near-identical name.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it largely does: stream_name is identified as the target stream and probe=True is explained in terms of what it actually retrieves (codecs, SDP, byte counters). The default value of probe is left to the schema, but the semantic meaning of both parameters is conveyed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get producer and consumer details for a specific stream') plus the key identifier, which cleanly separates it from get_server_info and list_streams. However it does not distinguish itself from the sibling probe_stream, which appears to cover the same probing function, leaving an ambiguity an agent must resolve by guessing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives one concrete usage cue: set probe=True to actively query codecs, SDP, and byte counters. That is implied guidance for the parameter rather than when-to-use guidance for the tool. It never says when to call this instead of the sibling probe_stream, or when probe=False (the default) is sufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.