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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavioral detail beyond that: results are ordered newest first, the comment field usually contains log lines, and results are paginated. It does not mention rate limits or whether maxAgeInDays combines with paging, so it is not fully complete.

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 short sentences with zero filler. The resource and its scope come first, then the returned fields, then a one-word pagination note — everything is front-loaded and nothing is redundant.

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?

With no output schema, the description usefully enumerates the return fields (time, categories, comment, reporter) and their ordering, which is exactly what an agent needs to interpret results. It stops short of explaining how paging terminates or how maxAgeInDays interacts with ordering, leaving a small gap for a paginated read tool.

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 100%, so all four parameters, including defaults and ranges, are already documented. The description only adds the word "paginated," which hints at page/perPage without adding syntax or format beyond the schema, 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 names a specific resource and scope: "the individual abuse reports filed against one address," plus the fields returned. That is clearly distinguishable from generic tools, though it does not explicitly contrast itself with get_network_report or get_country_report, which are the closest siblings.

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?

Usage is implied by "against one address," which tells the agent this is the per-IP variant, and "paginated" signals iterative paging. There is no explicit when-to-use vs. when-not statement or pointer to get_network_report for network-level aggregation, so routing is left to inference.

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