List Tasks

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

Without annotations, the description carries the burden. It discloses the effect of 'include_completed' and 'limit' on results, which adds some behavioral context. However, it omits details like ordering, pagination, or idempotency, leaving the agent with gaps.

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 with no wasted words. The description is front-loaded with the core behavior and effectively uses a parenthetical for the key parameter. It 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?

For a simple list tool with zero required parameters and no output schema, the description covers the essential behavior. However, it lacks details on ordering, error conditions, or connection to siblings like 'list_done', leaving some contextual gaps.

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 baseline is 3. The description adds value by explaining 'include_completed' switches between open and all tasks, and clarifies that 'limit' applies only when include_completed is true, enhancing understanding beyond the 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 tool lists tasks, specifying the default behavior (open tasks) and the parameter to include completed tasks. It distinguishes the tool's scope from siblings like 'add_task', but does not explicitly differentiate from 'list_done'.

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 tool versus alternatives like 'list_done' or 'complete_task'. The description implies usage for listing tasks but fails to provide exclusion criteria or when-not-to-use.

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