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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description goes well beyond them: everything deployed is deleted and unrecoverable, billing for a paid size stops at the destroy, and freed capacity returns to the organisation's playground memory budget. These are concrete consequence and side-effect disclosures an agent cannot infer from the hints.

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 sentences, both front-loaded: consequences first, precondition second. No filler, no restating of the tool name, and each clause carries distinct information.

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 and annotations that already cover the safety profile, the description supplies the missing postconditions (data loss, billing stop, budget return) and the pre-call workflow. It could say more about whether the destroy is immediate or asynchronous, but nothing essential for correct invocation is absent.

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 100%, and the single cluster_id parameter is fully documented in the schema itself, so the baseline is 3. The description's 'name and size' phrasing does not add syntax or selection detail for cluster_id beyond what the schema already provides.

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 ('Permanently destroy a playground environment') and pins down the scope with 'permanently', which separates it from non-destructive siblings like resize_playground or stop_cluster. Its emphasis on unrecoverability also distinguishes it from create_playground/delete_cluster in the sibling list.

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 an actionable precondition: state the environment's name and size from get_playground_status before proposing the destroy, which names a specific sibling tool to consult first. It stops short of explicit when-not-to-use guidance (e.g., 'if you only want to pause, use park/stop instead'), so it is strong but not complete.

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