list_abuse_reports

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

No annotations exist, so the description carries the full burden of disclosing behavior. It only says 'List', which implies a read-only operation, but it does not describe response shape, pagination, permissions, ordering, or whether the reports are summarized or full. This is minimal transparency for a list 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?

The description is a single six-word sentence with no wasted words. The operation and scope are front-loaded, making it easy to parse quickly.

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 one-parameter, no-output-schema list tool, the basic invocation is fully understandable: supply account_id and get a list of abuse reports. However, it lacks behavioral detail such as pagination or return shape, and it does not mention get_abuse_report as the way to retrieve a single report, so it is adequate but not thorough.

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 schema already documents account_id with 100% coverage, so the description does not need to explain it. The description adds no additional meaning about the account_id format or where it comes from, but the baseline of 3 applies because the schema handles 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?

States a specific verb ('List'), resource ('abuse reports'), and scope ('for an account'), making the core purpose clear. It is distinguishable from the sibling get_abuse_report by the plural resource and list verb, though it does not explicitly call out the alternative.

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 phrase 'for an account' provides useful scope context, indicating this is an account-level collection operation rather than a zone-level or single-item read. However, it gives no explicit guidance about when to use this instead of get_abuse_report, and no mention of filtering, pagination, or exclusions.

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