delete_account

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

Annotations already flag destructiveHint=true and readOnlyHint=false, but the description adds crucial behavior beyond them: the operation is irreversible, affects entire transaction history, first call only previews, and deletion requires both confirm: true and confirm_name set to the exact account name. This is exactly the safety context an agent needs.

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?

Three sentences, all information-dense and in priority order: destructive warning first, then the preview/confirmation mechanics, then the alternative. No filler or repetition of schema details.

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 tool with three simple parameters and no output schema, the description covers the essential behavioral flow: preview first, confirm with both safeguards, and prefer closing for retirement. An agent has enough to call the tool correctly and avoid accidental irreversible deletion.

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% and each parameter already has a meaningful description. The tool description adds value by explaining the interaction between confirm and confirm_name as complementary safeguards, and by clarifying that omitting confirm turns the call into a preview rather than an execution.

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 a specific verb and resource: 'Delete an account and its entire transaction history.' It clearly distinguishes this from related tools like delete_transaction and delete_category by emphasizing the account-level scope and destructive consequence.

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 gives explicit when-not-to-use guidance: 'Prefer closing an account when you just want to retire it.' It does not explicitly say 'use delete_account when you want permanent removal,' but that intent is strongly implied by the first sentence and the preview/confirmation flow.

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