List tasks

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

Discloses default compact view, pagination with limit/offset, and filtering behavior. Annotations already indicate read-only, which description reinforces.

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?

Three sentences that efficiently convey purpose, default behavior, filters, pagination, and an alternative. No wasted words.

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, but description explains return format (compact vs full) and pagination. Covers filtering, ordering, and when to use an alternative tool.

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 low (27%). Description enumerates filterable fields (type, status, product, label, search) and explains compact and pagination, but does not detail each parameter's meaning or format.

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?

Clearly states it lists features and/or bugs on a board with most-recent-first ordering. Distinguishes from sibling tools like get_metrics and get_task.

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?

Explicitly suggests using get_metrics for a pure overview, providing an alternative. Implicitly differentiates from other list tools by naming the resource and filters.

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