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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), and the description adds real context beyond that: edits are undoable, nothing reaches Amazon, BETA status, and tier-based export quotas. It does not detail what duplicate/undo actually mutate, but the added behavioral context is substantial.

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?

The action-to-parameter list is front-loaded and earns its place, but it is a dense run-on enumeration. The BETA/quota sentence is relevant but verbose relative to the calling task, and the whole block is not tightly structured.

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?

For a five-action tool with 0% schema description coverage and no output schema, the description supplies the per-action parameter mapping, the safety/undoability context, and a pointer to video_guide for the full per-action schema. The main residual gap is the absence of per-action type details, which it defers to video_guide.

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 0% and the schema only lists bare property names, yet the description maps each action to its parameters (e.g., duplicate needs projectId/expectedRevision/title/idempotencyKey) and names fields absent from the schema (aspectId, brandId, name, brand). This compensates well for the coverage gap, though it omits types and format constraints.

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 set (create/duplicate/undo/brand_update/look_save) against the 'Video Director' project resource, and the action= enumeration makes the scope concrete. It distinguishes itself from read siblings by naming video_guide as the companion catalog tool, but does not explicitly separate itself from video_delete or video_edit_apply.

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?

It tells the agent to 'Call video_guide first' and explains edits are undoable and stay inside Video Director, which is useful routing. However, it never states when to pick this tool over siblings like video_edit_apply or video_delete, so the when-to-use guidance remains implied.

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