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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety needs no restatement. The description adds real value beyond them by describing what is in each returned item and noting the default state filter, but it is silent on result volume, pagination, or ordering.

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 sentences, no filler, with the scoping filter front-loaded before the detail of what records contain. The list of incident types is somewhat run-on and could be tightened, but every clause carries information.

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?

An output schema exists, so return shape need not be explained, and annotations cover the safety profile. What remains essential for correct invocation — the state filter, its default, and the pointer to act_on_incident for remediation — is all present; the only omission, offset paging, is minor for a list tool whose default view is open incidents.

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 must carry parameter meaning. It explains the state filter and its default but never enumerates the accepted values (open/contained/resolved/expected), and the offset parameter for paging is not mentioned anywhere in the description. Partial compensation only.

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?

Names the resource (incidents) plus the scope (one state, open by default) and enumerates the three incident types it returns: unaccounted spend, runaway/stolen keys, and overcharges. It also states what each record carries (key, amount, flag reasons), which lets an agent distinguish it from act_on_incident or get_incident without opening a schema.

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?

'Incidents in one state (open by default)' establishes the browsing context, and the closing sentence routes action-taking to act_on_incident, so the read-vs-act split is explicit. It does not mention the other sibling options (get_incident, incident_evidence) for drilling into a single case, so the routing guidance is clear but incomplete.

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