delete_organization

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

Annotations already indicate destructive and non-read-only nature; description reinforces permanence and adds identifier behavior details (name vs ID). No contradictions. Adds useful behavioral context beyond annotations.

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, front-loaded with purpose and warning. Every word adds value; no redundancy. Excellent structure for quick comprehension.

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?

Given single parameter, annotations, and output schema, description covers all essential aspects: purpose, identifier options, caution, and use case. No gaps remain for agent decision-making.

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 describes params with 100% coverage but vague ('a string that will be trimmed'). Description adds that identifier can be an ID or exact name (if unique), adding crucial semantic meaning. Compensates for schema's minimal detail.

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?

Clearly states the tool permanently deletes an organization, specifies identifier options (ID or exact unique name), and gives a use case (cleaning up duplicates after merging). Distinguishes from sibling delete_* tools by its focus on organization deletion.

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?

Explicitly warns about irreversibility, recommends using ID for non-unique names, and suggests when to use (after merging data elsewhere). Provides clear context for selection vs. alternatives.

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