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

With no annotations, the description carries the full disclosure burden. It helpfully signals that results are truncated summaries rather than full records and routes depth to get_issue, but says nothing about read-only safety, ordering, or how paging beyond the limit works.

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 clauses, front-loaded with the core action and return shape, then filtering guidance, then the sibling pointer. No sentence is wasted.

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?

Since there is no output schema, the description compensates by naming the returned fields and noting they are short summaries. It lacks detail on result ordering and whether more results exist beyond the limit, which would matter for a listing tool.

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 projectId, limit, severity, and testRunId are already documented. The description adds only the intent behind two of them ('only what one run found', 'to triage') and says nothing about limit or projectId beyond the schema, so 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 and resource (list QA issues in a project) plus the exact shape of what comes back (id, title, severity, status). It explicitly distinguishes itself from get_issue, which returns full detail for a single issue, so an agent can pick the right tool 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?

Gives concrete guidance: pass testRunId to scope to one run, or filter by severity when triaging, and points to get_issue for detail. There is no explicit 'when not to use' (e.g., for cross-project listing or listing projects, which siblings cover), so it stops short of a 5.

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