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

Annotations already declare readOnlyHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds real value on top: it enumerates the observable pipeline state, exposes error reporting, and hints at polling cadence, plus an explicit negative scope ('Does not return the transcript') that prevents a wrong-expectation call.

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 sentences, zero filler: the first front-loads what the agent gets back, the second closes the one non-obvious gap (no transcript). Nothing is repeated from the annotations or schema.

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-value exposition is not required, and the description still gives an accurate summary of the payload plus the polling cue. Only minor gaps remain (auth requirements, error/failure semantics when the project does not exist or is not found).

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?

One parameter with 100% schema coverage; the schema already documents projectId as the project identifier. The description adds no syntax, format, or sourcing guidance for the ID, so the baseline 3 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?

The description names a specific verb+resource ('Detailed status of a project') and enumerates the returned contents (pipeline steps, error, clips, next action, polling delay), which lets an agent separate it from list_projects or get_clip. It stops short of naming any sibling explicitly, so differentiation is inferred rather than stated.

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?

Implied usage only: mention of 'next expected action' and a 'suggested polling delay' signals this is the status-polling call after starting a project, but the description never says when to prefer it over list_projects or retry_project, nor states prerequisites such as a project already existing.

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