search_advanced

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

With no annotations provided, the description carries the full burden. It only explains parameter formats (e.g., YYYY-MM-DD, UUID) but does not disclose what the tool returns, whether it is read-only, any rate limits, or other behavioral details. The output schema exists but is not referenced.

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 extremely concise: a single-line purpose statement followed by a clear bullet list of parameters. Every line serves a purpose with no redundancy. The purpose is front-loaded.

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 7 optional parameters and an existing output schema, the description adequately covers parameter meanings but lacks context about the return format, default filtering behavior, or interactions between filters. It feels sufficient for basic use but not comprehensive.

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 description adds meaning beyond the schema (which has 0% coverage) by providing descriptions for all 7 parameters, including format hints for dates (e.g., 'YYYY-MM-DD', '3d', '1w') and type constraints (e.g., UUID for area). However, the descriptions are minimal and do not clarify sources or constraints fully.

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 'Advanced todo search with multiple filters' and lists all filter parameters, making the tool's purpose evident. However, it does not explicitly differentiate from sibling tools like search_items or search_todos, which also search todos but may be simpler.

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 usage for complex filtering with multiple criteria, but it fails to provide explicit guidance on when to use this tool versus simpler search alternatives or what the prerequisites are. No exclusions or comparisons are made.

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