List Tracker issues

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld). The description adds genuine behavioral context beyond them: omitted filters are dropped, results are auto-paginated, and a return count exactly equal to limit is a 'more may match' signal. That pagination/truncation semantics is not derivable from the annotations or schema.

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 tight sentences with zero waste; the filter semantics are front-loaded and the pagination caveat follows immediately. Every clause earns its place.

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?

No output schema exists, so the description carries the burden of return behavior, and it does explain the truncation/pagination edge case well. It stops short of describing the shape of a returned issue, which is a minor residual gap.

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 all six parameters are already documented in the schema, which sets the baseline at 3. The description adds only the 'omitted filters dropped' default behavior, which is marginal extra meaning over the schema's null defaults.

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 states a specific resource (Tracker issues) and the filtering behavior, making the purpose clear. However, it never distinguishes this tool from close siblings like tracker_issues_search, tracker_issues_count, or tracker_issues_suggest, so an agent has no textual basis for picking this one over those.

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?

There is no explicit guidance on when to use this vs. the sibling search/count/suggest tools. The only usage-flavored content is the within-tool pagination hint (narrow filters or raise limit), which does not help alternative selection.

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