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

With no annotations provided, the description carries the transparency responsibility. It explicitly states 'Informational only. Read-only; price 0.0 (free),' plus 'heuristic' indicates non-definitive, and 'every contribution is returned in the rationale' discloses output behavior. This is strong disclosure beyond bare input schema.

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 two sentences, front-loaded with the core purpose, and every clause adds value (range, methodology, transparency, informational nature, cost). No filler or redundancy.

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?

Despite lacking an output schema, the description explains the score range and that a rationale with contributions is returned. It does not detail exact response fields or error handling, but the single-param simplicity and behavioral clues make it sufficiently complete.

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 coverage is 100%; the only parameter 'ip' is fully described as 'IPv4 or IPv6 address.' The description adds no additional parameter-specific detail, so the baseline 3 applies.

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 states the tool computes a 'transparent heuristic IP risk score (0-100)' from specified signals, using a specific verb and resource. It differentiates from sibling IP tools by emphasizing the composite nature and transparency (rationale returned).

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 description implies use for an overall risk score by combining classification, datacenter, and reverse-DNS signals, making it distinct from individual lookups like ip_reputation_asn_lookup. However, it does not explicitly name alternatives or state when not to use it.

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