bardo_account_deletion_request

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

Annotations indicate destructiveHint=true, which description confirms with 'permanent deletion' and 'no undelete'. Description adds extensive behavioral context: irreversible, requires multiple confirmations on different days, puzzle challenge, lapsed attempts start over. No contradictions.

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?

Description is fairly long but every sentence adds value, starting with the core purpose and irreversibility. It is well-structured with clear steps. Could be slightly more concise, but no unnecessary information.

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?

Given no output schema and 3 optional params, the description provides complete guidance on how to use the tool, including the multi-step process, puzzle requirement, and time limits. No important behavioral aspects are missing for an agent to correctly invoke the tool.

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 has 3 params with 0% description coverage. Description explains that omitting challenge_id and answer returns a fresh puzzle, adding meaning to those parameters. Session_token is not explained, but overall the description compensates well for the lack of schema descriptions.

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?

Description clearly states it requests permanent deletion of account and notes, distinguishes from note deletion by noting there is no grace period. It also explains the multi-step confirmation process, making the purpose specific and differentiating from siblings like bardo_account_deletion_cancel.

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?

Describes when to use (to initiate permanent deletion) and when parameters should be supplied or omitted. It explains the puzzle mechanism and that each confirmation needs a new puzzle. Some implicit guidance on not using for cancellation or status, but could be more explicit about alternative tools.

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