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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description is not carrying the safety burden. It adds the pagination note and the underlying API mapping (GET /v1/incident/search/list), but says nothing about default limit, maximum page size, or how offset interacts with results.

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 compact, front-loaded sentences: capability first, API mapping second. The filter enumeration is dense but useful. The raw endpoint citation is marginal value and the only slight filler.

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 read-only list tool with 14 fully documented parameters, no output schema, and no nested objects, the description covers purpose, filter surface, and pagination adequately. Missing details are minor (pagination defaults, result shape) and partly outside the description's remit given the rich schema.

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 100%, so the schema already documents all 14 filter parameters with their meanings and defaults. The description only restates the filter categories in prose and adds nothing about value formats, defaults, or combining behavior beyond what the schema provides. Baseline 3 applies.

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+resource ('Search/list incidents') and enumerates the filter dimensions (status, severity, team, user, search term, archived/snoozed, date range), which clearly separates it from the singular allquiet_get_incident and the mutation siblings. It does not explicitly name or route against a sibling, so it falls just short of a 5.

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 word 'Search/list ... with filters' implies this is the collection-browsing tool as opposed to get_incident for a single record, but there is no explicit when-to-use statement, no when-not, and no named alternative. Usage is inferable rather than stated.

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