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

With no annotations, the description carries the full burden. It transparently discloses that the action is irreversible, states the return value (deleted organization id and deleted flag), and even notes the token cost. It doesn't mention cascade effects on related data, but it adequately covers the most critical safety aspect.

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 four concise, purposeful sentences: purpose, prerequisite/parameter routing, irreversibility/return, and cost. Each sentence earns its place, with the main purpose front-loaded and no redundant 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?

Given the tool's modest complexity (2 params, 1 required, output schema present), the description covers all essential aspects: purpose, prerequisite workflow, parameter semantics, safety warning, return value, and cost. It is complete for an agent to select and invoke it correctly.

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% for both parameters, but the description adds operational meaning beyond the schema by instructing to call clerk.get_connected_accounts first and clarifying the behavior when clerk_instance_id is omitted. This contextual workflow is valuable.

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 states 'Permanently delete an organization from a connected Clerk application' with a specific verb, resource, and scope. It clearly distinguishes this tool from sibling deletion tools like delete_organization_domain or delete_organization_membership by targeting the organization itself.

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?

It provides explicit usage guidance: 'Call clerk.get_connected_accounts first' and explains when to pass clerk_instance_id vs omit it for the default account. It gives clear context and prerequisites, though it does not mention explicit alternatives or exclusions.

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