Search Proton Pass Items

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

Annotations provide readOnlyHint=true, which is consistent. The description adds behavioral details: case-insensitive substring search, client-side filtering from the item list, and that it returns only summaries. This goes beyond annotations with useful context about execution and limitations.

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 sentence with a brief follow-up note, front-loading the action and scope. Every word is necessary; no redundancy or filler.

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 presence of an output schema (not shown but noted), the description need not detail return values. It covers the search scope, filtering mechanism, and links to the complementary tool pass_get, providing complete context for a simple search operation.

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 100%, but the description enriches by explaining that the search applies to specific fields (name, URL, note, vault) and that results are client-side filtered from the item list, adding semantic value beyond the schema descriptions.

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 verb 'search', the resource 'Proton Pass item summaries', and specifies it is case-insensitive substring search across multiple fields (name, URL, note, vault). It also distinguishes from the sibling tool pass_get by noting it returns summaries only.

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 explains when to use this tool (to search summaries) and explicitly directs to use pass_get for decrypted content, providing clear guidance. It does not list other alternatives but the context is sufficient.

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