task_list

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

No annotations provided, so description carries full burden. It only mentions 'list', implying read-only, but doesn't explicitly state that it is safe, non-destructive, or discuss rate limits or authentication needs. Missing behavioral context.

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?

Description is concise (9 lines including examples), well-structured with Args, Returns, Examples. Every sentence adds value; front-loaded with purpose.

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 no annotations and low complexity (2 optional params, simple list return), the description is complete: covers purpose, parameters, return fields, and provides examples. No output schema exists, but return fields are listed.

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 0%, but description adds meaning: explains 'limit' default and 'filter_status' possible values with examples. Provides context beyond schema, though case sensitivity or exact formatting is not specified.

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 'List recent transfer and delete tasks', providing a specific verb and resource. It distinguishes from sibling tools like task_show (detailed view) and task_event_list (events).

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?

Examples imply usage (e.g., filtering by status), but no explicit guidance on when to use this tool versus alternatives like task_show or task_event_list.

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