verify_magic_link

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

Discloses user creation, single-use token, and 15-minute expiry. No annotations provided, but description covers key behaviors. Lacks details on rate limits or auth requirements.

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, no filler. Front-loaded with main action. Highly 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?

Covers inputs, outputs (access_token + refresh_token implicitly), and key behaviors. No output schema, but description sufficiently explains what the tool returns. Could mention possible errors.

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 descriptions are brief ('The project ID', 'The magic link token from the email link URL'). Description adds context that token comes from URL and is a magic link token, adding value beyond schema.

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?

Clearly states the tool exchanges a magic link token for access and refresh tokens, and creates a user if needed. Distinct from sibling 'request_magic_link' which sends the link.

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?

Implied usage after receiving a magic link token. Does not explicitly state when not to use or alternatives, but context is clear.

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