Запросить код смены пароля

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

No annotations are provided, so the description carries the burden. It discloses that it sends an email with a code, which is useful, but doesn't mention side effects like invalidating previous codes, email throttling, or errors for non-existent emails. That would be valuable context.

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?

One sentence, no fluff, front-loaded with the main action. Efficient.

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 there is no output schema and no annotations, the description is thin for a tool that initiates a password reset flow. It would benefit from noting that the code is sent for the reset_confirm step.svg.

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 100% with a clear description of the email parameter (account email). The description adds 'password recovery' context, but the parameter is already well-documented in the schema, so minimal extra value.

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 states the action (sends a code to email) and resource (password recovery), but it doesn't explicitly name the tool's purpose relative to siblings like 'wata_password_reset_confirm'. It is clear what it does but doesn't distinguish it from the reset flow.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it's for starting password reset, but doesn't mention that it should be used before wata_password_reset_confirm, nor any conditions like account existence or rate limits.

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