Search Items

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

Annotations already indicate readOnlyHint=true. The description adds value by revealing the underlying CLI command and the unreliability of custom field searches, which is useful behavioral context. No contradictions or missing critical traits like rate limits or authentication requirements.

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 at two sentences, with the first sentence front-loading the core purpose. Every word contributes meaning, no redundancy.

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?

Critical contextual information is missing: there is no output schema, and the description does not explain the return format, pagination behavior (despite having a limit parameter), or what happens when no results are found. For a search tool with multiple optional filters, this leaves significant ambiguity.

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?

All 8 parameters have descriptions in the input schema (100% coverage), so the tool description adds minimal new semantic value. The phrase 'by text and filters (org/folder/collection/url)' summarizes the main parameters but does not provide details beyond what the schema already says.

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 'Search vault items by text and filters' and lists the filter types, making the tool's purpose immediately obvious. It also distinguishes the tool by noting the underlying command and a specific limitation (custom field search reliability), which differentiates it from sibling tools like keychain_get_item or keychain_list_collections.

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 explicit guidance on when to use this tool versus alternatives. The description implies it is for text-based searching with filters, but does not mention when not to use it (e.g., when you need exact item retrieval via keychain_get_item) or provide comparisons to sibling search tools.

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