search_todos

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

The description lacks details beyond 'search and filter'. No disclosure of pagination, read-only nature, authentication needs, or other behavioral traits. With no annotations, the description bears full responsibility.

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 concise sentence, but it is underspecified. Efficient in word count but sacrifices necessary context, making it borderline adequate.

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 five parameters and sibling tools, the description is incomplete. It does not explain output, pagination (though 'limit' is present), or when to use each filter. Lacks crucial context for correct invocation.

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?

With 0% schema description coverage, the description adds minimal meaning: it lists filter fields but provides no details on accepted values or formats. Compensates slightly by identifying filterable attributes but insufficient for effective use.

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 the tool searches and filters to-dos, listing specific filter fields (status, priority, plan, project). This distinguishes it from sibling tools like 'get_todo' which retrieves a single to-do, and other search tools like 'search_projects'.

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 such as 'get_todo' or 'search_tasks'. No mention of when not to use it or prerequisites.

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