list_tasks

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

Discloses default status_id=1 and how to get closed tasks, plus project resolution. No annotations exist, so description carries the burden; it could mention non-destructive nature but it's implicit.

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-loaded with purpose, no redundancy, every sentence adds information.

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?

Covers purpose, parameters, and behavior adequately. No output schema, but description doesn't need to cover returns; missing explicit mention of pagination or limits, but acceptable for a list 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 coverage is 100%, and description adds value beyond schema fields: explains default status_id and config-file fallback for project resolution, which schema descriptions lack.

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 'List tasks in a Kanboard project' with specific verb-resource pair. Differentiates from siblings by mentioning default active tasks and how to list closed ones, and explains project resolution.

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?

Provides clear when-to-use: listing tasks, with default active and option for closed. Does not explicitly mention alternatives, but the default behavior is well-defined.

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