find-tasks

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the description's role is lighter. It adds that the tool searches and returns tasks with specific filter options and a required filter constraint, which aligns with annotations. No contradictions.

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 consists of two efficient sentences. The first lists the tool's capabilities, and the second adds a necessary constraint. No wasted words, front-loaded with key 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?

The description covers the core functionality and constraint. With 12 parameters, 100% schema coverage, and an output schema, the description is sufficient. It lacks explicit mention of pagination (cursor/limit) but that is detailed in the schema. Minor gap in explaining relationship with siblings.

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 description coverage is 100%, so the baseline is 3. The tool description summarizes filter options but does not add new meanings beyond the schema parameter descriptions. It provides a high-level overview, which is helpful but not essential given schema completeness.

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 explicitly states 'Find tasks' and lists all filtering criteria: text search, project/section/parent container, responsible user, labels, raw Todoist filter string, or saved filter. It distinguishes from siblings like find-completed-tasks and find-tasks-by-date by covering general task searching with multiple filter types.

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 states 'At least one filter must be provided,' which is a clear precondition. However, it does not explicitly compare with alternatives like find-tasks-by-date or when to use this vs. other search tools. The constraint is helpful but lacks explicit when-to-use guidance.

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