item_search

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

No annotations are provided, so the description bears full responsibility. It reveals one behavioral trait (client-side fallback when no vault), but omits critical details like read-only status, permission requirements, rate limits, or side effects. For a search operation, this is insufficient.

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 very concise with two sentences, the first covering the core purpose. However, it sacrifices necessary detail, which limits its effectiveness despite the efficient structure.

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?

Missing output schema, no parameter explanations, and sparse behavioral context. For a tool with four parameters (including a limit), the description fails to cover pagination, return format, error modes, or the semantics of includeArchived. The agent would lack sufficient information to use the tool correctly.

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 description coverage is 0%, and the description does not explain any of the four parameters (query, vaultId, includeArchived, limit). The mention of 'title/tags/category' hints at the query's role but is too vague to guide correct usage.

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 action ('Search') and resource ('item overviews') and specifies search criteria (title/tags/category). This distinguishes it from items that retrieve a single item or vault-level operations.

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 only mentions a behavioral detail about vault selection ('If no vault is provided, the server searches every visible vault client-side'), but offers no guidance on when to use this tool versus alternatives like password_read or item_get_metadata. No exclusions or prerequisites are stated.

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