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

Annotations only cover the safe-read profile, yet the description adds real behavioral context: a hard 25-second cap, the sender-verification filter, the warning that a verified sender is not necessarily trustworthy, and that mail content is untrusted and never followed. This is meaningful disclosure an agent cannot get from the 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?

Front-loaded with the action and time bound, then parameter guidance, then safety caveats. Dense but every sentence carries information; only the final trust note is slightly verbose.

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?

There is no output schema, and the description compensates by naming the fields an agent should inspect (link_host, subject, sender). Combined with parameter and timing guidance, it is nearly complete, though the 'to' parameter and the response shape's exact structure remain unspecified.

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 description coverage is 0%, so the description must carry the load, and it explains since, from_domain, other_hosts, and the 25s bound on wait. The required 'to' parameter is left unexplained, which is the only notable gap.

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?

States a specific verb and resource: waits up to 25 seconds for a sender-verified verification link. The 'link' framing implicitly separates it from the sibling wait_for_code, but it never names that sibling or explicitly contrasts the two.

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?

Gives concrete operating instructions: set since to the sign-up start time, set from_domain to the expected service, and use other_hosts:true for other hosts. It lacks an explicit statement of when to prefer this over siblings like wait_for_code or list_recent_mail.

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