search_todos

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

Discloses case-insensitivity and default filter scope. No annotations provided, so description carries full burden. Lacks details on pagination or sorting, but key behaviors are covered.

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 with no unnecessary words. First sentence states primary purpose, second adds a key conditional behavior. Front-loaded and compact.

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 existence of output schema, return values need not be described. Covers main purpose, parameter meanings, and default vs. extended behavior. Could mention search limits or ordering but sufficient.

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 0%, yet description explains both parameters: query is for name containment, include_completed extends search to Logbook. Adds meaning beyond schema structure.

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?

Verb+resource: 'Search to-dos' indicates a search operation on to-dos. It specifies the filter (name contains query, case-insensitive) and distinguishes from sibling tools like list_todos (likely listing all) and get_todo (by ID).

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?

Provides guidance on default behavior (only open to-dos) and how to modify with include_completed. Does not explicitly contrast with alternatives but implies usage for name substring search.

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