list_tasks

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

With no annotations, the description must fully disclose behavior. It briefly notes the output format (summary view by status/priority) but omits important details like read-only nature, pagination, authorization requirements, or limits. The description is insufficient for a safe agent invocation.

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, clear sentence that communicates purpose and key features without waste. However, it could be slightly more structured (e.g., separate filtering from output summary) but remains effective.

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?

Given the tool has 5 optional parameters and no output schema or annotations, the description should explain how filters behave (e.g., AND logic), the output format in more detail, and any limitations. The current description leaves significant gaps for an agent to use correctly.

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 the baseline is 3. The description adds context that filters are optional and output is organized, but it does not clarify filter combination logic or the meaning of empty strings in enum fields. Thus it provides marginal added value over 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 action ('Lists all tasks'), the resource ('tasks'), and key features: optional filtering and organization by status and priority. It effectively distinguishes from sibling tools like 'get_task' (single task) and 'search_tasks' (full-text search).

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?

No explicit guidance on when to use this tool over siblings such as 'search_tasks' or 'list_archived_tasks'. The description implies it is for listing all tasks with filters but does not provide exclusion criteria or mention alternatives.

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