list_tasks

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

No annotations are provided, so the description carries full burden. It states it lists tasks (a read operation) but does not disclose behavioral traits like pagination behavior (beyond limit/offset in schema), how filters combine (AND/OR), or any side effects. The description is partially transparent but lacks explicit detail.

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 sentence of 16 words, efficiently front-loading the core action and essential details. No extraneous or redundant 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?

Given the tool has 17 parameters and no output schema or annotations, the description is too sparse. It does not explain the return structure, default sorting, or how multiple filters interact. For a complex listing tool, this leaves significant gaps for an AI agent.

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?

The input schema has 100% description coverage, so each parameter is already documented. The description only loosely summarizes the filters ('status, flags, tags, projects, date ranges, and text search') without adding new semantic meaning or clarifying combination logic. With high schema coverage, a baseline of 3 is appropriate.

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 verb 'list', the resource 'tasks', and the source 'OmniFocus'. It lists the available filters, making the purpose unmistakable. This distinguishes it from sibling tools like get_task (single task) or create_task (mutation).

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 it is for general listing with filters, but it does not explicitly guide when to use this vs. more specific sibling tools like get_project_tasks, get_inbox_tasks, or get_flagged_tasks. There is no mention of when not to use or what alternatives exist.

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