search_tasks

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

No annotations provided, so description carries burden. Discloses default exclusion of trashed tasks, inclusion of checklists, case-insensitive matching, and behavior for blank queries. Lacks details on sorting, pagination default behavior, or result format (though output schema exists).

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?

Very concise: one-line purpose followed by parameter list. No redundant language. Well-structured for quick comprehension.

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?

Covers core functionality and parameter behaviors well. Missing context on result sorting, differentiation from 'search_advanced', and potential performance considerations. Output schema mitigates need for return value explanation.

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 0%, but description fully compensates by explaining each parameter's effect and defaults (e.g., blank query returns empty list, include_trashed default false, include_checklists default true, limit/offset optional). Adds context the schema lacks.

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?

Description clearly states full-text search across specific fields (titles, notes, checklist items) and notes case-insensitive substring matching. However, it does not differentiate from sibling tool 'search_advanced' which may offer more advanced features.

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?

No guidance on when to use this tool versus alternatives like 'list_all_tasks' or 'search_advanced'. Missing when-not conditions or preferred scenarios.

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