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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context beyond that: nothing about pagination, ordering, what happens when statuses is omitted/empty, or whether resolved exceptions are still returned.

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?

A single front-loaded sentence with no filler and no restating of the tool name. It is efficient, though arguably under-sized relative to the undocumented parameters it leaves behind.

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?

No output schema exists, so the description would need to sketch the return shape (exception entries, their statuses, any pagination) and the default filtering behavior. It provides none of that, leaving an agent unable to predict what comes back or how to narrow the list.

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 0% for 3 parameters, so the description carries the full burden — and it says nothing about projectId, siteId, or statuses. In particular the statuses array with its five enum values and default of [] is ambiguous (does empty mean all statuses or none?), and the description does not resolve it.

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?

Clear verb+resource (list ... exceptions) plus a plain-language gloss — 'cases the outreach agent stopped on and left for a human' — that tells an agent what an 'exception' actually is. It partially differentiates from the neighbouring list_outreach_automation_runs and get_outreach_automation_overview, but never names them, so the boundary between 'exceptions' and 'runs' must still be inferred.

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?

No when-to-use guidance, no prerequisites, and no mention of the natural follow-up tool (update_outreach_automation_exception) or of when to prefer this over list_outreach_automation_runs. The agent is left to guess at the workflow context entirely.

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