find-tasks

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

Annotations already declare this as read-only, idempotent, and non-destructive, lowering the burden. The description adds useful behavioral context by stating the mandatory filter requirement and by indicating that a raw Todoist filter string or saved filter by ID/name is accepted. No contradictions with annotations exist.

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 that front-loads the primary action and then efficiently lists the supported filter dimensions, ending with a crisp usage requirement. Every phrase adds value with no repetition or filler.

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 12-parameter schema with 100% description coverage and an output schema, the description need only provide high-level orientation, which it does effectively. It covers the main filter categories and the mandatory-filter rule, though it leaves detailed combination constraints and pagination to the schema.

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%, so the baseline is 3, but the description goes beyond the schema by grouping parameters into search categories and explicitly naming filterIdOrName as the saved-filter parameter. It also conveys the cross-parameter constraint that at least one filter must be provided, which is not visible from the schema's required list.

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 uses a specific verb ('Find tasks') and resource, then enumerates all major filter dimensions: text, project/section/parent container, responsible user, labels, raw Todoist filter, and saved filter. This distinguishes it from sibling tools like find-tasks-by-date and find-completed-tasks by making the general search scope explicit.

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 clearly states the use case: find tasks by various filters, and adds the important prerequisite 'At least one filter must be provided.' However, it does not explicitly mention when to prefer sibling tools like find-tasks-by-date or find-completed-tasks, so the guidance is implied rather than explicit.

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