reclaim_list_tasks

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

Annotations declare readOnlyHint and idempotentHint. The description adds behavioral context: default filter excludes ARCHIVED/CANCELLED tasks, and explains that 'COMPLETE' status does not mean the task is done. This goes beyond annotations without contradiction.

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 front-loaded with the purpose, then default, then the critical note. It is slightly long due to the important status explanation, but each sentence is necessary to avoid misinterpretation. Could be slightly more concise, but 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 simplicity of the tool (one parameter, no output schema), the description covers purpose, default behavior, and the critical status nuance. It doesn't explain return format, but that's acceptable. It is sufficiently complete for the 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% with parameter descriptions. The description adds nuance: default behavior of 'active' filter (excluding ARCHIVED/CANCELLED) and the critical note about 'COMPLETE' status. This adds value 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 'Lists Reclaim.ai tasks' with a specific verb and resource. It distinguishes from sibling tools like reclaim_get_task (single task) and reclaim_create_task (create) by focusing on listing. The description also specifies default filter and important status nuance.

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 provides explicit context on when to use this tool (listing tasks) and how to interpret the 'COMPLETE' status, guiding the agent to treat 'COMPLETE' tasks as active. It doesn't explicitly mention when not to use it or compare with siblings, but the important note serves as a usage guideline.

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