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

The annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds critical behavioral context beyond them: deletion is permanent, an initial call without confirm only previews and deletes nothing, and user confirmation is required before the destructive call. This preview/confirm workflow is not visible in the annotations and meaningfully reduces accidental deletion risk.

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?

Three compact sentences, front-loaded with the core action ('Permanently delete testimonials'), followed by the required safety workflow and the preferred alternative. Every sentence carries necessary information with no filler.

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 destructive tool with no output schema, the description covers what an agent most needs: that deletion is permanent, the mandatory two-step confirmation flow, and a safer alternative for non-destructive intent. Combined with annotations that declare destructiveness, no critical calling information is missing.

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 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining the confirm flag's role in the two-step workflow (used only after the user approves the preview) and reinforcing that testimonial_ids are the targets of a permanent delete. It does not add format details, but the workflow context is a genuine value-add.

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 starts with a specific verb and resource: 'Permanently delete testimonials.' It immediately distinguishes the tool from the sibling 'moderate_testimonials' by naming the alternative and its hide action. An agent can identify the tool's operation and its scope 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?

It provides explicit when-to-use guidance via a two-step confirmation procedure (call without confirm to preview, then with confirm=true after user approval) and an explicit when-not-to-use alternative ('Prefer moderate_testimonials action=hide when the user just wants something off their site'). Nothing about selection is left to inference.

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