search_passwords

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

Beyond the readOnlyHint annotation, the description adds critical behavioral details: case-insensitive matching, metadata-only returns, and no secret values exposed. This fully sets expectations for the tool's behavior.

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 two concise sentences, front-loading the action, then clarifying the output scope and follow-up step. No unnecessary words or 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?

For a simple search tool, the description provides all necessary context: what it searches, how it matches, what it returns, and how to proceed to obtain the actual secret. The sibling tool landscape makes the purpose and usage unambiguous.

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 single 'query' parameter is described as a substring to match on label/username/url, which aligns with the tool's purpose. The tool description adds case-insensitivity, making the parameter's meaning fully clear.

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 tool searches saved passwords by case-insensitive substring across label, username, or URL, and explicitly notes it returns metadata only. This distinguishes it from siblings like list_passwords (which likely lists all) and get_password (which retrieves a specific secret).

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?

It explicitly instructs to use get_password with an id from results to reveal a secret, providing a clear next step. The case-insensitive substring behavior and metadata-only return give concrete guidance on when to invoke this tool versus alternatives.

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