initiate_account_recovery

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

Annotations indicate readOnlyHint=false (writes) and openWorldHint=true (side effects). The description says it creates a support ticket and provides instructions, which is transparent. However, it does not elaborate on side effects like emails or system state changes. Given openWorldHint, more detail would be beneficial.

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 a two-sentence summary that is front-loaded and contains no unnecessary words. Every sentence adds value.

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 mutation tool with open world implications, the description is functional but lacks details on what happens after recovery is initiated, any required prerequisites, or expected outcomes. More context would improve completeness.

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 33% (only contact_info has description). The description adds general context for the parameters (e.g., reason is about why recovery is needed), but does not explain each parameter in detail. It partially compensates for low schema coverage.

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's purpose: 'Start account recovery for users who cannot receive the reset email.' It distinguishes from the sibling 'initiate_password_reset' by specifying the scenario (cannot receive email). It also describes the outcome: creates a support ticket and provides instructions.

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 implicitly gives usage context: use when the user cannot receive the reset email. It does not explicitly list when not to use or mention alternatives, but the context is clear enough.

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