get_backplane_media_streams

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

The description discloses the tool's behavior as a read operation ('Get media stream statistics'), which is consistent with the annotations (readOnlyHint=true, destructiveHint=false). The annotations already cover safety and idempotency, so the description adds sufficient context.

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?

The description is extremely concise: two sentences. The first states the purpose, the second documents the parameter with a dependency hint. Every word earns its place; no redundancy or filler.

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?

Given the existence of an output schema and comprehensive annotations, the description provides the essential context: the tool's purpose and parameter source. It does not detail return values, but the output schema presumably covers that. Slightly lacking in broader usage context, but still sufficient.

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?

The only parameter, backplane_id, has 0% schema description coverage. The description adds meaningful guidance by stating 'Backplane id from list_backplanes', informing the agent that the ID comes from that specific source. This compensates for the missing schema description.

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?

The description clearly states the tool's verb ('Get'), resource ('media stream statistics'), and context ('for a backplane connection'). This distinguishes it from siblings like 'get_backplane' which retrieves the backplane itself, and 'get_backplane_history_media_streams' which likely retrieves historical data.

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?

The description provides a helpful guideline for the backplane_id parameter, instructing to obtain it from 'list_backplanes'. However, it does not explicitly compare to other tools like 'get_backplane_history_media_streams' or indicate when to use this tool over alternatives.

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