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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), so the description focuses on semantics instead: the persistence model (one thread per problem per page), the meaning of the default status filter ('everything still broken'), and pagination. That default-filter clarification is genuinely valuable because an agent could otherwise assume all statuses are returned. Return shape/ordering is not described, keeping it below a 5.

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?

Three short sentences, zero filler, with the resource model front-loaded before filters, pagination, and the id hand-off to get_issue. 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?

For a six-parameter, all-optional list tool with rich annotations and no output schema, the description covers the resource model, the default filter behavior, pagination, and the id needed for follow-up calls. Minor gaps remain around ordering of results and how project scope interacts with the other filters.

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 coverage is 83%, so parameters are already well documented; the description largely restates the filter dimensions (code, URL, status) and the status vocabulary. It adds the useful gloss that the default status set means 'everything still broken', but nothing about limit/offset behavior or the id-or-slug flexibility of project_id beyond what the schema says.

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 names the resource precisely — persistent issue threads, one per problem per page — and enumerates the status values, so an agent knows exactly what is being listed. The final sentence pointing to get_issue makes the boundary with that sibling explicit. Only the verb is implicit (carried by the name rather than the prose).

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?

Usage is implied rather than stated: 'Each item carries the issue id for get_issue' signals that detail lookup is a separate call. There is no explicit when-to-use versus acknowledge_issue/unacknowledge_issue, and no statement of prerequisites such as needing a project_id.

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