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

Annotations declare this is not read-only, not idempotent, and not destructive, but say nothing about partial-failure semantics. The description adds genuinely useful behavior beyond that: only incomplete pages are retried and already-successful pages are preserved, which tells the agent the operation is scoped rather than a full re-render.

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 short sentences with zero filler; the scope of the operation is front-loaded in the first sentence and the preservation guarantee in the second. Nothing is wasted.

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 single-parameter mutation with no output schema and annotations covering the safety profile, the description is minimally adequate. It omits what 'incomplete' means, whether the retry is synchronous, and what the caller gets back or should do if pages remain incomplete.

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 0% for the single required carousel_id parameter, and the description says nothing about it. The schema alone conveys the pattern and required-ness, so the description cannot be blamed for the format, but it also adds no meaning such as where the id comes from or what qualifies a carousel as retryable.

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 ('retry') and resource ('incomplete carousel pages'), which is more precise than a generic retry. It sits alongside retry_batch and retry_image_pack, and while the resource name distinguishes it, there is no explicit contrast drawn with those siblings.

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 implied rather than stated: 'incomplete carousel pages' hints this is for recovering partially rendered carousels, but there is no when-to-use trigger, no prerequisite (e.g. after a failed render), and no reference to any alternative tool.

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