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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so safety is partially covered. However, the description adds almost nothing: it doesn't disclose that status changes (e.g., resolved/dismissed) affect the automation pipeline, doesn't mention the assignee mutation at all, and doesn't describe side effects on retrying exceptions.

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 short sentence with no padding, which is structurally clean. However, the brevity comes at the cost of under-specification rather than efficiency, so it is only middling on this dimension.

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 mutation tool with six parameters, four required, zero schema description coverage, and no output schema, this description is far too thin. An agent lacks the identifier semantics, allowed status values context, and consequence of resolution needed to invoke it correctly.

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%, so the description carries the full burden, yet it only alludes to status and notes. It omits three required identifiers (projectId, siteId, exceptionId) and the assigneeUserId parameter entirely, leaving most parameters undocumented anywhere.

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 states a verb and resource ('change ... of an exception') and names two of the mutable fields, so the general intent is inferable. But the verb is generic ('change' rather than 'resolve' as the title says), and it gives no differentiation from siblings like list_outreach_automation_exceptions or set_outreach_automation_status. Purpose is merely adequate.

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 (e.g., obtaining exceptionId via list_outreach_automation_exceptions), and no indication of which status transitions are permitted. The agent is left to guess when this tool applies versus adjacent automation tools.

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