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

With no annotations, the description carries the transparency burden. It discloses that no API key is needed and that functionality is 'limited', which is useful operational context. However, it does not describe rate limits, error behavior, or what the response contains beyond the three flag categories.

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 a single telegraphic sentence with no redundant words. Core purpose and the most important constraint ('no key, limited') are front-loaded. It is concise without being a tautology, though it borders on under-specification.

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 tool with one undocumented parameter and no annotations, the description leaves important gaps: it doesn't explicitly state the input is an email address, doesn't differentiate from nearby siblings, and the 'limited' claim is vague. The presence of an output schema helps, but the description alone is not enough to invoke the tool correctly.

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 explain the 'q' parameter. It says 'for email' which implies the query is an email address, but it never explicitly maps 'q' to an email input or specifies format. This is insufficient for an agent to know exactly what to pass.

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 clearly identifies the tool's domain (email reputation via emailrep.io) and the type of data returned (malicious/spam/breach flags). It distinguishes itself from siblings by naming a specific service, though it lacks an explicit verb and is fragmentary.

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 phrase 'no key, limited' gives some context about when this tool is appropriate (quick checks without authentication) but does not explicitly state when to use it versus alternatives like hibp_email or leakcheck. Usage context is implied rather than stated.

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