verify

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

No annotations, so description carries full burden. It discloses that on success the account is verified, session is logged in, and the token is saved to disk for all future sessions – a critical side effect. It also warns that recovery codes are shown once and should be saved.

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?

Three sentences, front-loaded with the action, then important side effects and warnings. No wasted words.

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?

The description covers the main purpose, when to use, side effects, and response contents (api_key, recovery_codes). With no output schema, explaining the response is valuable. For a simple 2-param tool, this is complete.

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 2 params (email, code) with 0% description coverage, so description must compensate. It indirectly describes them: 'email verification code' implies the code parameter, and the email used at registration is implied. It doesn't provide format details, but for simple string params this is sufficient.

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 'Confirm the email verification code from `register`' – a specific verb, resource (the verification code), and source (register). This clearly differentiates from sibling `verify_login`.

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 explicitly ties the tool to the `register` flow, implying this is the step after registration. It doesn't explicitly name alternatives, but the context is clear enough for the agent to know when to use it vs `verify_login`. No exclusions stated.

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