video_project_recipe_replay

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

No annotations are provided, so the description carries the full disclosure burden. It implies a mutation (creating a 'new durable project revision'), which is the only behavioral signal, but says nothing about idempotency, whether an existing revision is overwritten, permission requirements, or how source_bindings resolve. For a 4-required-param write tool this is a significant gap.

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 front-loaded sentence with no wasted words, which is structurally fine. However, the brevity reflects under-specification rather than disciplined concision given the tool's complexity.

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?

The tool is a mutation with five parameters, nested objects, and no annotations; an output schema exists so return values need not be described. But with zero parameter documentation and no behavioral disclosure, the description leaves the agent without enough to invoke it correctly. Only the bare purpose is conveyed.

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% across five parameters, including a nested 'artifact' object and a 'source_bindings' string map, and the description explains none of them. It adds no meaning beyond the property names: what an artifact contains, what a source binding maps, or what base_revision_id defaults to are all left opaque.

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 ('replay') and a clear input→output transformation: a portable recipe becomes a new durable project revision. This implicitly distinguishes it from the inverse sibling video_project_recipe_export, though it never names that sibling. The jargon ('recipe', 'durable revision') is domain-specific but coherent.

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 when-to-use guidance, no prerequisites, and no named alternatives. An agent cannot tell from the description whether this is the right tool versus video_project_recipe_export or video_init_project without inspecting schemas. Usage must be fully inferred.

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