List audio streams on a call

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

Annotations already declare readOnlyHint=true, so 'Read-only' is redundant. However, the description adds genuinely useful context beyond the annotations: pagination is stateless, nothing is persisted between calls, and results span both active and stopped streams. It stops short of describing return ordering or rate limits.

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?

Three front-loaded sentences with the purpose first and no filler. Minor redundancy between 'Pagination is stateless' and 'Nothing is saved between calls' costs a point.

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?

With no output schema, the description carries the return-value burden and does so ('status, WebSocket URL, track and audio format'). Read-only and pagination behavior are covered; only the call_uuid parameter and ordering semantics are left unexplained.

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 coverage is low (33%); only limit has a schema description. The description explains limit/offset as stateless pagination, which adds value, but it also references page/per_page that do not exist in the schema, which risks confusion, and it never explains call_uuid.

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 (List) and resource (audio streams on a Vobiz call), and scopes it as 'both active and stopped'. This clearly distinguishes it from the singular get_audio_stream sibling and from the mutation siblings start_audio_stream/stop_audio_stream.

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?

Usage is implied (enumerate all streams, active and stopped), which is enough to distinguish it from get_audio_stream, but no sibling is named and no explicit when-to-use/when-not guidance is given.

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