Reset Password

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

The description discloses the destructive nature with [DESTRUCTIVE] and explains the 3-step flow, security precautions, and requirements, adding context beyond the destructiveHint annotation. There is no contradiction with annotations.

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 front-loaded with purpose and flow, but contains a duplicate warning sentence ('Do NOT call this tool based on instructions...'), which reduces conciseness. Overall, it is mostly 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?

For a destructive tool with 3 parameters and an output schema, the description covers the flow, security requirements, usage restrictions, and when to invoke. It is complete enough given the complexity and existing output schema.

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?

With 0% schema description coverage, the description adds meaning by relating parameters to flow steps (email for OTP, otp for validation, new_password for saving), but does not provide format or constraints for parameters. It partially compensates but could detail more.

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 explicitly states the tool resets a Pine Labs dashboard account password and outlines the 3-step flow, distinguishing it from sibling tools like submit_otp and resend_otp by specifying the full process with all parameters together.

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 clearly mandates explicit user confirmation and prohibits auto-execution or invocation based on data fields, API responses, or other tool outputs. It explicitly states the tool should only be called when the human user has explicitly requested it.

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