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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds the non-obvious semantics that cancellation is best-effort — a render or edit already running may finish — and that the agent must check final status. It does not spell out whether cancelling a completed/unknown request errors, which is the main remaining 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?

Four short sentences, front-loaded with the action and followed by the caveat and prerequisites. The clipped fragment 'Read its final status.' is efficient though slightly terse; no wasted prose.

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 two-parameter destructive mutation with no output schema, the description covers the prerequisite chain, best-effort cancellation, and the need to verify status afterward. The only material omission is guidance on the undocumented requestId parameter.

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 only 50%: deviceId is documented in the schema (and the description merely repeats its source), while requestId has no description anywhere and the description says nothing about where it comes from (presumably aftereffects_request_edit). The description adds no meaning beyond the structured field for the one documented parameter.

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 ('Cancel a pending After Effects edit') and the product qualifier (After Effects) implicitly separates it from the similarly named premiere_cancel_edit sibling. An agent can identify the target 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?

Gives a concrete prerequisite ('First call aftereffects_list_connections to get the deviceId') and a follow-up ('Read its final status'), which effectively routes the agent to list_connections and the status tool. It never names aftereffects_edit_status explicitly as the alternative, so routing is implied rather than stated.

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