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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine scoping context ('Changes that clip's project; preserves the other clips'), clarifying the blast radius of the destructive operation, but says nothing about reversibility, permissions, or rate limits.

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 tight, front-loaded sentences with no filler: purpose plus examples first, scope constraint second. Well-structured, though the second clause is the only scope information and could be slightly more precise.

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 values need not be described. However, for a destructive, 4-parameter mutation tool with only 25% schema coverage, the description leaves the repair modes and permission/authorization requirements unexplained, which is a meaningful gap.

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 low (25%). The examples ('screen demo', 'captions away from faces') indirectly illustrate two repairMode enum values, but the description never explains repairMode, clipId, workspaceId, or idempotencyKey — including the two required parameters — so it does not compensate for the coverage gap.

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 ('Request a layout repair for one managed clip') and gives concrete examples of the operation ('preserving a screen demo or moving captions away from faces'). This lets an agent understand the action, though it never explicitly contrasts with near-siblings like clips_manage, clips_recover, or batch_update_timeline_clips.

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?

Usage is only implied: the agent can infer this is for fixing the layout of a single clip. There is no explicit when-to-use vs when-not guidance and no named alternative for related tasks such as batch-editing or manually updating timeline clips.

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