forgot_password

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

No annotations are provided, so the description must carry the burden. It discloses that the tool sends an email and does not complete the reset itself, which is useful. However, it omits details such as rate limits, error behavior for invalid emails, or session invalidation.

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 core action, and every sentence adds value. No redundancy.

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 one-parameter tool with no output schema and no annotations, the description covers the action, the follow-up steps, and the fact that the actual reset is handled on the website. It lacks some edge-case details but is adequate for simple use.

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 schema has a single 'email' parameter with 0% description coverage. The description's phrase 'by email' clarifies the parameter's role. But it adds no format or validation details, and the parameter's meaning is largely self-evident from its name.

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 uses a specific verb 'Request' and resource 'password-reset code by email', and clarifies the follow-up steps, distinguishing it from sibling auth tools like login and use_token.

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?

It states this tool only requests the reset code, and instructs to complete reset on website then log in with new password or use_token, giving clear context for when to use this vs subsequent login steps. It doesn't explicitly state when not to use, but the flow implies it.

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