List tasks

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

Beyond the readOnlyHint annotation, the description discloses ordering ('most-recent first'), pagination behavior (limit/offset), default compact view, and the effect of setting compact:false. It also mentions context budget optimization, adding value beyond annotations.

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 sentences front-load the purpose and key features. Every sentence adds value: listing, ordering, filtering, pagination, compaction, and alternative tool reference. 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 the description explains the default return format (compact one-line view) and how to get full details. It also mentions pagination handling. This is sufficient for a list tool, though it could specify whether the full task objects match those from get_task.

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 low (20%), but the description compensates by listing filterable fields (type, status, product, label, search) and explaining pagination and compaction parameters. It also clarifies the 'most-recent first' order, which is not in 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 'List features and/or bugs on a board, most-recent first', specifying the verb (list) and resource (tasks on a board), and distinguishes from siblings like 'get_board' or 'get_task' by implying a list operation with filtering.

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 provides usage context: pagination for large boards, compaction toggle, and explicitly suggests 'Use get_metrics for a pure overview' as an alternative. However, it doesn't specify when not to use this tool or exclude certain scenarios.

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