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

Annotations already declare destructiveHint=true and openWorldHint=true, so the bar is lower; the description still adds the meaningful detail of what is discarded and replaced (script plus library assets). It does not cover authorization needs, rate limits, or how idempotency affects repeated calls.

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, zero filler, with the action and its effect front-loaded and the disambiguation placed second. Every clause earns its place.

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?

There is no output schema, so the description should ideally say what the call returns or what state the piece ends up in, and it should clarify the required idempotency key. It covers the core behavior and the sibling distinction, but leaves the agent under-informed for a destructive operation with two undocumented required parameters.

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 two required parameters, so the description carries the full burden and adds nothing about pieceId or idempotencyKey. For a destructive, non-idempotent-looking write, the absence of any explanation of idempotencyKey semantics is a real 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 ('Replace a failed job piece with a freshly written script and new library assets') and contrasts it with a re-render. It distinguishes the concept from the sibling retry_content_render but never names that tool, so routing requires a small inference.

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?

The second sentence effectively gives a when-not-to-use condition: if you only want to re-render the existing script, this is the wrong action. The alternative is described by behavior rather than by tool name, and no prerequisites (e.g. the piece must be in a failed state) are spelled out.

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