delete_account

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

With no annotations provided, the description carries the full burden. It discloses that safeguards exist (deletion blocked with children or transactions), which is valuable behavioral context beyond what 'delete' implies. It doesn't mention permissions/auth requirements, but the safeguard disclosure is meaningful for a destructive operation.

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 compact (three short sections) and front-loaded with the purpose. The safeguards and parameter format details are useful. Slight improvement possible by integrating parameter info more naturally, but overall well-structured and lean.

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?

This is a single-parameter destructive tool with zero annotations but has an output schema. The description covers the purpose, failure conditions (safeguards), and parameter formats. It's reasonably complete for a simple delete tool, though it could note whether the operation is reversible or describe output behavior.

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 description coverage is 0%, so the description must compensate. It does: 'name' parameter is explained as an account ref accepting three formats (full path, %short GUID, or full 32-char GUID). This adds substantial meaning beyond 'Name' in the schema.

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 tool deletes an account from the chart of accounts, a specific verb+resource combination. It distinguishes from sibling tools like delete_account_slot, delete_transaction, and delete_budget by specifying the 'chart of accounts' resource context.

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 mentions safeguards prevent deletion if the account has children or transactions, giving the agent context on when deletion would fail. However, it doesn't explicitly name alternative tools or state when NOT to use this tool versus other delete operations, though the purpose is clear enough to infer.

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