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

The description says 'Report' and 'Returns the updated abuse confidence score,' implying a state-changing write operation, while annotations declare readOnlyHint=true. This is a direct contradiction: the description describes a write while the annotation claims read-only. This inconsistency is critical for an agent deciding whether to invoke the tool.

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?

Two concise sentences, front-loaded with the main action, followed by the key requirement and return value. Zero waste.

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?

The description covers purpose, key requirement, and return value, and the schema/annotations fill in parameter and safety details. However, it lacks usage context to differentiate from sibling tools and the contradiction with readOnlyHint creates confusion, leaving notable gaps.

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% with all four parameters described in detail, including category IDs and examples. The description's mention of '18,22' for DDoS + SSH brute force merely repeats what the schema already provides, adding no new parameter semantics.

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 reports an abusive IP address to AbuseIPDB, with a specific verb ('Report') and resource. It distinguishes from sibling tools like check_ip, which likely checks reputation instead of submitting a report.

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 usage for reporting abusive IPs but does not explicitly state when to use it versus alternatives such as check_ip or get_blacklist. It lacks exclusions or explicit 'use this when' guidance.

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