Filter Tasks

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

No annotations are provided, so the description must convey behavior. It discloses an important behavior: 'All filters are AND-combined'. It does not explicitly state that it performs a read-only operation or describe return format/pagination, but the filter semantics are reasonably transparent.

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?

Two sentences, front-loaded with the core purpose, no fluff. Efficiently conveys the key combination behavior.

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 6-parameter filter tool with no annotations or output schema, the description provides basic functionality but lacks usage guidance relative to the many sibling task tools. It doesn't mention scope (e.g., returns all matching tasks) or pagination, though the AND-combination note is helpful. Overall adequate but with gaps.

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 covers all parameters with descriptions, so baseline is 3. The description adds that filters are AND-combined, which explains interaction between parameters. It also groups parameter types (project, priority, date ranges, text search), adding semantic context beyond individual descriptions.

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 function as 'Advanced task filtering' and lists specific criteria (project, priority, date ranges, text search). It distinguishes from sibling list tools by emphasizing combined criteria, though it does not explicitly contrast with ticktick_search_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 use when multiple criteria need to be combined ('Combine multiple criteria'), and notes that all filters are AND-combined. However, it does not specify when not to use it or name alternatives, such as ticktick_search_tasks for simple searching.

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