Remove Account

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

Discloses that first call returns a conflict with options, that deletion is permanent but recoverable for 30 days, and that active transactions block deletion. Without annotations, this provides good behavioral context, though the two-call sequence could be more explicit.

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 the action and key behavior, no unnecessary words. Efficient and clear.

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?

Covers the main workflow and conditions. Lacks details on the exact output after successful operation and the format of the conflict response, but is fairly complete given no output schema.

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 covers 100% of parameters with descriptions. The tool description does not add extra meaning to parameters beyond what the schema provides, so score at baseline 3.

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 removes a financial account, specifies two removal modes (archive/delete), and mentions the conflict response. This distinguishes it from sibling remove_* tools by focusing on financial accounts and the unique two-phase process.

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?

Explains the conflict-driven flow and condition for deletion (no active transactions), guiding when to use archive vs delete. Does not explicitly mention when not to use, but context from siblings clarifies it's for financial accounts only.

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