delete_organization

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

Annotations already provide destructiveHint=true, idempotentHint=true, and readOnlyHint=false, but the description adds nothing beyond the bare action. It does not mention whether the deletion is permanent, cascades to related resources, or requires special authorization.

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?

The description is a single sentence with no filler, so it is easy to parse and front-loaded. However, the brevity is achieved by omitting useful context, so it is concise but not exceptionally well-rounded.

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 one-parameter delete operation, the schema plus annotations supply the essential call information. The lack of any return-value hint or side-effect description leaves it minimally complete rather than fully specified.

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?

The schema fully documents the only parameter ('id' with description 'Organization ID to delete'), so the high coverage baseline applies. The description adds no further meaning to the parameter, such as format or prerequisites.

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 uses a specific verb ('Delete') and identifies the resource ('an organization'), so an agent can tell this apart from sibling delete_* tools by resource. It adds no detail about deletion semantics, so it is clear but not fully differentiated.

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?

There is no guidance on when deletion is appropriate, what prerequisites exist (e.g., admin permission, empty organization), or which alternative tool to prefer. The only use case is implied by the tool name, which the description simply restates.

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