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

Annotations already declare readOnlyHint=true, so safety is covered. The description still earns credit for disclosing the HTTP endpoint and, importantly given there is no output schema, the return envelope { meta, response }, which tells the agent to expect pagination metadata wrapper rather than a bare array.

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 compact paragraph that front-loads the purpose before the endpoint and parameter list; nothing is padded. It reads as terse API-reference shorthand, 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?

For a zero-required-param read tool with full schema coverage and readOnly annotations, the description supplies the missing pieces: endpoint identity and return shape. Only the absence of guidance on selecting this over get_issue/sibling listers keeps it from being fully complete.

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 every parameter is already documented with defaults, ranges, and filter syntax. The description merely echoes the parameter names (_page/_limit/_fields/_filters/_search) without adding format or interaction detail, 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 issues — support/service tickets"), and the ticket gloss disambiguates the overloaded word "issue." It does not explicitly distinguish itself from singular get_issue or from accelo_request, so it falls 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?

No when-to-use guidance, no exclusions, and no direction on how it relates to get_issue or other list_* siblings. The description only documents surface mechanics (endpoint and query-string options), leaving the agent to infer when this is the right call.

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