Wait for project

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

Goes well beyond the readOnlyHint annotation by disclosing that the call blocks, what the timeout produces, and how to continue after a timeout. It also enumerates the return payload including stageProgress semantics ("else null") and the partial-stage etaSec, which is real behavioral context an agent cannot get from annotations.

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?

Front-loaded with the blocking behavior and the timeout escape hatch before the return shape. The dense parenthetical type listing for stageDetail is slightly harder to parse than prose or a shallow field list, but every clause carries information.

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?

No output schema exists, so the description carries the return-value burden and does so thoroughly (id, status, stage, stageProgress, stageDetail, error, clips). For a two-parameter long-poll read tool, nothing needed to invoke or interpret it is missing.

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 100% and documents both id (source: create_project/list_projects) and timeoutSeconds (1-120, default 60). The description only alludes to timeoutSeconds passing, adding no syntax or semantics beyond the schema, so the baseline applies.

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 plus the blocking scope: "Block until the project is done or failed, or timeoutSeconds pass." It also names the contrasting sibling (get_project) so an agent can distinguish blocking vs non-blocking reads immediately.

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?

Gives explicit when/when-not guidance: use this to wait, use get_project "instead for a non-blocking look with full clip details." It even covers the post-timeout path — "on timeout the same with hint 'Still running': call it again" — leaving no retry inference to the agent.

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