list_tasks

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds the scoping constraint of 'recent' tasks and optional status filtering, which provides useful context about the data returned, similar to date-range scoping in the TDQS example.

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, concise sentence with no filler. It front-loads the verb and resource and conveys both the default behavior and optional filtering clearly.

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 two-parameter list tool with read-only annotations, the description is adequately complete. It covers the core functionality and the optional filter, and the lack of an output schema does not hurt because 'list' implies an array return. However, it does not specify ordering details or default limit, which might require the agent to rely on schema defaults.

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?

With 0% schema description coverage, the description must compensate. It explicitly mentions the 'status' parameter as an optional filter, giving semantic meaning. However, the 'limit' parameter is not discussed in the description, though its schema constraints (min/max) provide some self-explanatory information, leaving partial compensation.

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 recent tasks with an optional status filter, using a specific verb and resource. It distinguishes itself from sibling tools like get_task (single task) and get_task_tree (hierarchical view) by focusing on a flat list of recent tasks.

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 implies usage for retrieving a list of tasks but does not explicitly state when to prefer this tool over alternatives like get_task or get_task_tree. There are no exclusions or alternative references, leaving the agent to infer based on the tool name.

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