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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful ordering (newest first) and optional-filter semantics, but says nothing about pagination or how cursor pages behave, leaving a notable behavioral gap.

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 short sentences with the resource and ordering front-loaded, then the sibling disambiguation. Extremely economical, though the telegraphic style borders on under-specification rather than clean conciseness.

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 full schema coverage and no output schema, the description covers the resource, ordering, optional filters, and the sibling alternative. The only omission is pagination/cursor behavior, which is a minor gap given the schema documents the cursor.

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 (appId, limit, range, cursor, issueId, environment) is already documented in the schema. The description echoes the environment/range filtering but adds no syntax or format detail 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 and resource ('An issue's events, newest first') and explicitly contrasts with the sibling get_event ('reads one whole'), so an agent can route between the two. The phrasing is somewhat fragmentary but the purpose is unambiguous.

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?

Names the alternative (get_event) and its distinguishing behavior of returning a single full event, giving clear context for when to list vs. fetch one. It does not state exclusions or prerequisites, but the sibling routing is explicit.

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