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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=false. The description adds genuinely new behavioral context beyond those flags: it changes no picture and spends no credits, and that identical retries retain the originally quoted revision. The tension between 'records acceptance' and destructiveHint=true is left unexplained, but no direct contradiction exists.

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 short sentences, front-loaded with the action and scope; the clarification that it changes no picture and spends no credits earns its place by pre-empting credit-safety concerns.

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 a rich input schema, an output schema, and strong annotations, the description covers the essentials for calling this tool. It only falls short on routing relative to adjacent accept/approve siblings, which an agent working in this dense tool family would still have to infer.

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 100% and all three parameters are documented in the schema, including the expectedStills pairing rule and revisionId source. The description restates the revision and shot/asset pairing at a higher level but adds no syntax or format detail the schema lacks. 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?

States a specific verb and resource: 'Record the customer's acceptance of the complete saved key-look picture set.' It scopes precisely to the key-look stills set, which distinguishes it from the many other storyboard write/approve siblings without needing to open their schemas.

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?

The description tells the caller what to supply ('the exact revision and shot/asset pairs reviewed') but gives no when-to-use guidance versus nearby siblings such as studio_storyboard_approve or studio_storyboard_stills_confirm, and no stated preconditions. Usage is implied rather than directed.

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