Search Proton Pass Items

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

Adds behavioral context by stating 'Returns summaries only', which goes beyond readOnlyHint annotation. Informs that search covers specific fields (names, URLs, notes), but could mention pagination or rate limits.

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?

Two sentences efficiently convey action, scope, and crucial behavioral note. No extraneous content.

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?

For a single-parameter tool with output schema and annotations, the description covers what the tool does, what it returns, and how it relates to a sibling. No missing critical information.

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 description enriches the 'query' parameter by specifying it applies to full-text search across names, URLs, and notes, providing context beyond the schema's minimal description.

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 clearly states it performs full-text search across Proton Pass item names, URLs, and notes. It distinguishes from sibling pass_get by noting that pass_get retrieves decrypted content, and from pass_list by implying search functionality.

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?

Explicitly advises using pass_get for decrypted content, guiding when not to use this tool. However, does not mention alternatives like pass_list for listing without search, so lacks complete exclusion guidance.

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