list_audience_abuse_reports

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

Annotations already indicate readOnlyHint=true (safe, no destructive actions). Description adds context: pagination via offset, required list_id from list_audiences, and return format. Does not mention rate limits or other constraints, but sufficient for a list operation.

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?

Concise yet complete: single-line purpose, usage context, and structured Args/Returns sections. No wasted words, front-loaded with core action.

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 list tool, covers purpose, parameters (except account), return format, and pagination. With output schema available but not shown, description compensates reasonably. Missing account parameter detail is a minor gap.

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 has 4 params with 0% description coverage. Description adds meaning for list_id, count, and offset (type, range, default, usage). However, account parameter is not mentioned, leaving its purpose unexplained. Adequate but not fully compensating for missing param.

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?

Clearly states the tool lists abuse reports filed against an audience, uses specific verb 'list' and resource 'audience abuse reports'. Distinguishes from sibling get_audience_abuse_report by mentioning it for single report inspection.

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?

Explicitly says to use for monitoring deliverability health and identifying spam campaigns, and directs to get_audience_abuse_report for detailed inspection of a single report. Provides clear when-to-use and alternative.

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