katto_retitle_clip

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false): it discloses quota consumption per regeneration, the 'limit' error on exhaustion, that a caller-supplied title costs nothing, that the call is synchronous, and that video quota is not used. This is exactly the extra behavioral context a mutation tool needs.

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-loads the core action, then packs the mode/quota behavior, the style list, return shape, and quota disclaimer into dense sentences with no filler. Every clause conveys actionable 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?

With no output schema, the description supplies the return shape ({ title, clip_index, regenerated }), covers both execution modes, the error condition, and cost behavior. Nothing an agent needs to invoke it correctly 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 the schema already documents that 'style' is ignored when 'title' is given and that 'title' is free, so the description mostly reinforces structured data. It adds the quota interaction but little parameter syntax or format detail beyond the schema; 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 ('Change a clip's title') that is unmistakably distinct from siblings like katto_add_hook or katto_adjust_clip. An agent knows exactly what the tool does without opening the schema.

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?

Clearly branches usage: without 'title' the AI generates and spends a monthly allowance unit (failing with a 'limit' error when exhausted), while supplying 'title' saves exact text for free. This makes both modes and their costs explicit, but no sibling alternatives are named.

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