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

With no annotations, the description carries the full burden. It does disclose the underlying mechanism (holehe) and breadth (120+ sites), which is useful behavioral context. However, it does not state whether it is passive/read-only, whether it requires authentication, rate limits, or any limitations.

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 front-loaded sentence with no filler. It immediately states the capability and includes a concise parenthetical implementation note.

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 simple one-parameter lookup with an output schema, the description still omits essential input semantics for 'q' and provides no usage guidance. It identifies the broad purpose but is not complete enough to invoke the tool confidently without inspecting the schema.

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 single parameter 'q' is not described in the schema or in the description. The phrase 'this email' hints that q may be an email address, but it does not identify the parameter, its format, or that it is optional with a default empty string.

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 a specific resource and query: checking which of 120+ sites have an account for an email, using holehe. It is clear enough to select the tool, but it does not distinguish this from the sibling email_crosssite or explain why 'email_registration' differs.

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?

There is no explicit when-to-use guidance, prerequisites, or alternative tools named. The description implies a use case, but does not help an agent choose between this, email_crosssite, email, or other email OSINT siblings.

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