stream_rigging_task

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

No annotations are provided, so the description carries the full behavioral burden. 'Until it completes' hints at a long-lived blocking call, but nothing is said about how updates are delivered, whether the call blocks the agent, what happens on timeout, or behavior if the task already finished or failed.

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?

A single short sentence with no filler, so nothing is wasted, but the terseness comes at the cost of necessary specification rather than being efficient completeness.

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 annotations, no output schema, and zero schema description coverage on two parameters, the description is far too thin for a streaming/blocking tool. An agent cannot tell what it will receive, how long it will wait, or how timeout affects the call.

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% and neither parameter is mentioned in the description. The 'timeout' parameter is completely undocumented, and 'until it completes' arguably conflicts with the existence of a timeout knob, leaving the agent to infer its semantics.

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 ('stream updates for a rigging task'), which is clearly distinguishable from retrieve_rigging_task and list_rigging_tasks by the streaming verb. It never explicitly contrasts itself with those siblings, so it falls short of a 5.

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?

No guidance on when to stream versus calling retrieve_rigging_task repeatedly, nor any prerequisites such as the task needing to exist or be in progress. The only contextual hint is the trailing 'until it completes', which is incidental rather than a usage rule.

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