search_omnifocus_tasks

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

No annotations are provided, and the description does not disclose any behavioral traits. The tool accepts no parameters, making it unclear what is being searched or what the expected behavior is (e.g., full text search, keyword matching).

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 phrase that is under-specified rather than concise. It lacks structure and does not earn its place; it provides no useful information beyond the tool name.

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?

With no parameters and no output schema, the description is completely inadequate. It does not explain what the tool searches, how results are returned, or any limitations. A search tool should at minimum indicate what can be searched.

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 input schema has zero parameters with 100% coverage, but the description adds no meaning beyond the empty schema. A baseline of 4 would apply if the description clarified the purpose of having no parameters, but it does not.

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 is a tautology: it repeats the tool name verbatim ('Search OmniFocus tasks') without adding any detail about what the tool does. It fails to distinguish from sibling 'list_omnifocus_tasks', which likely serves a similar purpose.

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_omnifocus_tasks' or 'search_notes'. A search tool without parameters is confusing and lacks any context for appropriate use.

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