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

No annotations are provided, so the description carries the full burden. It usefully discloses the data surfaces checked (Gravatar graph, disposable, breach/paste), but omits read-only status, auth requirements, rate limits, and input handling details.

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?

One compact, front-loaded sentence with no filler. The parenthetical '(mosint)' and terse colon-separated list are slightly cryptic, but the text is appropriately concise for a lookup tool.

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?

An output schema exists, so return values need not be described. The description identifies the data surfaces, but the missing parameter semantics and lack of usage guidance mean the agent is not fully equipped to call the tool correctly, though the simple one-parameter shape limits the damage.

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% and the sole parameter 'q' is never mentioned in the description. The agent must guess that 'q' is an email address from the tool name alone; the description does not compensate for the schema 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 the domain 'Email Identity' and lists specific surfaces (Gravatar graph, disposable check, breach/paste), so the agent can tell it is an email-identity aggregator. However, it is a noun phrase rather than a clear verb+resource and does not distinguish itself from siblings like gravatarfull, disposable, breach_aggregator, or emailrep.

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?

No when-to-use guidance, prerequisites, or alternatives are provided. The description only says what the tool covers, leaving the agent to infer appropriate contexts from the name and the sibling list.

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