Get All Tasks

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

No annotations are provided, so the description carries the safety burden. 'List' reasonably implies a read-only operation, but the description does not explicitly confirm no side effects, nor does it mention pagination, ordering, or other behavioral traits.

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, efficient sentence. It immediately states the verb and resource, adds a clarifying parenthetical ('checklist items'), and contains no redundant or filler content.

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 simple list operation with one parameter and an output schema available, the description covers the essential purpose and scope. It could be slightly more complete with explicit read-only or usage-routing guidance, but nothing critical is missing for correct invocation.

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?

There is only one parameter, cardId, and the schema gives no description for it. The phrase 'on a card' clarifies that cardId identifies the owning card, but it does not explain the ID format or how to obtain it. The description adds some meaning but does not fully compensate for the 0% schema coverage.

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 uses a specific verb ('List') and a clear resource ('all tasks (checklist items) on a card'). The word 'all' distinguishes it from the sibling get_task, which retrieves a single task, and clarifies the tool's scope.

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 intended use is implied: call this when you need all checklist items for a given card. However, it does not explicitly state when to prefer this over get_task or mention any exclusions or alternative tools.

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