search_passwords

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

With no annotations provided, the description carries the full burden. It discloses a critical behavioral trait: the tool returns metadata only and never actual passwords. This is essential for managing user expectations and security. It does not mention other behaviors like pagination or read-only nature, but the key risk is covered.

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 that is front-loaded with the action and resource, then immediately clarifies the key limitation. No filler or redundant information.

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?

The tool has 8 optional parameters, no output schema, and no annotations. The description clarifies the core purpose and the fact that only metadata is returned, but does not describe what metadata fields are included or how results are structured. This is a gap, though the schema covers filtering options.

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 input schema has 100% coverage with descriptions for all 8 parameters, so the description does not need to explain parameters. The description adds no parameter-specific value beyond what the schema already provides, but the schema is self-sufficient.

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' and the resource 'password entries in IT Glue', making the purpose unambiguous. It also differentiates from sibling tools like get_password by noting it returns metadata only, not actual passwords.

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 implies when to use this tool vs alternatives by explicitly stating it returns metadata only, not passwords. This suggests that if actual passwords are needed, another tool (such as get_password) should be used. However, it does not explicitly name the alternative tool, so the guidance is somewhat implicit.

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