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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds useful behavioral context: returned counts for the environment and range, the unresolved tab default, and cursor-based paging. It stops there and says nothing about ordering guarantees or the shape of returned issues beyond counts.

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?

The operator enumeration is dense and load-bearing for q, but it is crammed into one sprawling sentence mixing defaults, search syntax, and pagination, making it hard to parse in one pass. The tab/sort context should be separated from the search-language catalogue for cleaner front-loading.

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 9-parameter, no-required-argument list tool with no output schema, the description covers defaults, counts in the response, the full q search language, and cursor paging, which is nearly everything an agent needs. It omits only the interaction/precedence among tab, q, and range, which would make it 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 coverage is 100% so the baseline is 3, but the description goes well beyond the schema for q, enumerating the search language (words, /regex/, field:value, negation with -/!, OR, ranges, wildcards, comparisons) that the schema only labels as 'the search, as Issues reads it.' It also confirms the unresolved tab default. Remaining parameters rely on the schema, which already documents them.

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 resource (issues) and scope (as the dashboard lists them, with per-environment/range counts), and the mention of tab/sort/q makes it clearly the list endpoint. It is distinguishable from get_issue and list_issue_events, though the phrasing 'as the dashboard lists them' is slightly indirect rather than a crisp verb+resource statement.

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?

Discloses a default ('a tab, unresolved by default') and the pagination mechanism, which implies intended use, but offers no explicit when-to-use versus siblings (e.g., get_issue for a single issue) or when-not-to-use guidance.

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