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

Annotations already declare destructiveHint=true and idempotentHint=false, but the description adds substantive context: the deletion cascades to all teams/owners and the operation is gated by a two-step CONFIRMATION_REQUIRED/confirmToken handshake. It stops short of stating that the deletion is irreversible, what permissions are needed, or what the final response contains.

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, no filler. Destructive scope is front-loaded and the procedural step follows immediately.

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, non-idempotent, no-output-schema tool, the description covers the essential contract: what is destroyed and how the confirmation loop must be driven. Missing only secondary details (irreversibility, permission requirements, failure modes such as an expired token).

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%, so the baseline is 3, but the description earns more by explaining the stateful semantics of confirmToken (empty first call, then the token from the CONFIRMATION_REQUIRED answer with identical arguments) — meaning the schema does not fully convey on its own.

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 ('Delete an organization') plus the cascade scope ('and all of its teams (owners)'), which distinguishes it from delete_team, remove_team_from_organization and delete_account in the sibling list. An agent can select this 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?

Gives a clear, actionable protocol ('tell the user what will happen, then call again with the SAME arguments plus confirmToken') that governs when and how the tool is invoked. It does not name alternative tools (e.g. delete_team for a narrower scope, update_organization instead of deleting), so the alternative-selection guidance is incomplete.

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