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

With no annotations, the description carries the full burden of disclosing behavior. It states the output (authoritative abuse email) and the backend (RIPEstat), but does not mention side effects, whether it is read-only, network dependencies, rate limits, or error handling. This is a significant gap for a tool that presumably makes an external API call.

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 very concise and front-loaded, stating the purpose in a single phrase. However, it relies on a noun-phrase format with parentheses, which is telegraphic rather than a clear sentence. It contains minimal information while being appropriately sized for a simple 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?

Although the output schema exists, the description leaves critical context unaddressed. It fails to explain the meaning of the 'q' parameter, which is essential for correct invocation. Given the large set of sibling tools, the description does not provide enough context to disambiguate when this tool should be used.

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?

The input schema has a single parameter 'q' with no description and 0% schema coverage. The description does not mention the parameter, its expected format, or what value should be passed (e.g., IP address, domain, ASN). The description adds no semantic meaning beyond the schema's bare property name.

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 as returning the authoritative abuse email for a given entity, and mentions the RIPEstat backend. It is specific about the resource (abuse email) and the source, but does not explicitly differentiate itself from sibling tools like whois or rdap that might also offer abuse contact data.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention exclusions, prerequisites, or when another sibling would be more appropriate. The only implied usage is from the tool name and description, but no explicit context is given.

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