issues_list

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

No annotations are provided, and the description only mentions 'paginated' which hints at listing behavior but does not disclose read-only status, destructive actions, authentication needs, or rate limits. The description carries the full burden but provides minimal behavioral context.

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 description is a single sentence that is front-loaded and efficient, containing no fluff. However, given the complexity of 12 parameters, a slightly more detailed description could improve usability without losing 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?

The description lacks details about pagination behavior (default page size, max pages), return format, filter syntax, and relationships between parameters. With no output schema, the description is insufficient for an agent to fully understand the tool's behavior and results.

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?

With only 17% schema description coverage, the description adds no parameter-specific meaning beyond the overall context of 'issues (bug tasks without sprint)'. It does not explain any of the 12 parameters, their usage, or constraints, failing to compensate for the poor schema.

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 clearly states the action ('Get paginated list'), the resource ('issues'), and provides a specific definition ('bug tasks without sprint'), which differentiates it from sibling tools like tasks_list or backlog_list.

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?

The description implies usage for listing bugs not in a sprint but does not explicitly state when to use this tool versus alternatives like tasks_list. No exclusions or alternative tool names are mentioned.

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