delete_client

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

With no annotations, the description carries full transparency burden. It discloses that the client is archived, not permanently deleted, and that historical project and billing data are preserved. This provides important behavioral context, though additional details (e.g., permissions, reversibility) are absent.

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 concise sentence that front-loads the action and key behavior. Every part is essential, with no wasted words.

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 simple delete/archive tool with one parameter and no output schema, the description fully covers the necessary context: what the tool does (archive), what happens to data (preserved), and the parameter needed. No additional information is required.

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 the single parameter 'client_id', so the baseline is 3. The description adds no additional semantic information beyond what the schema provides, as both state the parameter's purpose.

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 clearly states the action ('Delete (archive) a client') and the specific resource ('client'), and distinguishes from other deletion tools by clarifying that it archives rather than permanently deletes, preserving historical data.

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?

The description explains the archival behavior and why historical data is preserved, giving implicit guidance on when to use this tool (when archival is desired). It lacks explicit when-not-to-use or alternative tool references, but the context is clear enough for agent decision-making.

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