delete_manual_account

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

The destructiveHint annotation is supplemented well by the description: it discloses that transactions, rules, recurring items, and balance history can be optionally removed, and explicitly warns that both deletion options are irreversible. This adds meaningful behavioral context beyond the annotation.

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 and well-structured: the primary action is front-loaded, the optional behaviors are summarized in a single sentence, and the irreversibility warning is placed directly after. No filler or redundant detail is present.

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 a simple required parameter and fully documented optional flags, the description covers the core operation, the cascading deletions, and the irreversibility warning. An agent has enough information to invoke the tool correctly without missing critical details.

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?

The input schema already documents all three parameters with 100% coveragecars. The description's mention of transactions, rules, recurring items, and balance history mostly mirrors the schema's property descriptions rather than adding new semantic meaning, so it stays at the schema-covered baseline.

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 opens with a specific verb and resource: 'Delete a manually-managed account.' This immediately identifies the operation and, alongside sibling tools like delete_manual_crypto, clearly distinguishes this as the deletion tool for manual non-crypto accounts.

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 how to use the optional cascade flags, which is useful for invoking the tool correctly. However, it does not explicitly state when to prefer this tool over sibling deletion tools such as delete_manual_crypto or delete_account_balance_history, leaving that distinction to be inferred from the tool name.

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