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

Annotations already declare destructive=true and idempotent=false, and the description adds real value on top: local disks are deleted while retained volumes and backups continue to be billed, which is a cost consequence an agent cannot get from structured fields. It also implies the operation is asynchronous by telling the caller to poll status, though it never states what happens on a repeat call or partial failure.

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 short sentences, front-loaded with the action and scope, then the destruction/billing consequence, then the follow-up step. No filler; nothing is buried.

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?

Covers what is destroyed and how to verify completion, which is most of what matters for a two-parameter destructive tool with no output schema. However, it leaves the caller guessing what the call returns and which tool confirms release, and the zero-coverage parameters are never unpacked.

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%, so the two parameters carry no documentation. The description indirectly motivates confirm_local_data_loss by warning that local disks are deleted, and 'owned rental' hints at what order refers to, but neither parameter is explicitly explained or constrained.

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 with scope: 'Terminate every node in an owned rental.' That is concrete and clearly different from siblings like emt_rent or emt_cancel_experiment, but it never names an alternative, so the agent must infer the boundary rather than being told it.

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?

Implies when to use it (you hold an owned rental and want it gone) and adds useful follow-up guidance ('Inspect status until release is confirmed'), but gives no when-not conditions, prerequisites for ownership, or a pointer to whichever sibling reports release status.

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