list_passwords

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

With no annotations, the description carries the behavioral burden. It clearly discloses that password values are not included, that output_format changes field richness, and that save_to_file persists results to a temp file and returns its path. It does not explicitly mention that the operation is read-only, but the verb 'list' implicitly conveys this.

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 opens with a concise, information-dense summary, then uses a clean Args list with one-line semantics per parameter)Skip The Returns section is brief. No redundant filler, and all sentences earn their place.

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 description covers all parameters, return type, and the file-saving edge case, which is sufficient for choosing inputs. It lacks explicit comparison with sibling list/search tools and does not describe pagination iteration behavior, but those are minor gaps given the strengths elsewhere.

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%, but the description fully compensates by documenting every parameter with meaningful context: filter semantics, pagination defaults (page starts at 1, max page_size 1000), output_format options, and save_to_file behavior. This goes well beyond the bare schema.

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?

States a specific verb and resource: 'List passwords from IT Glue' with the critical caveat 'without password values.' This distinguishes it from get_password which implies retrieving a single record including values, though it does not explicitly compare itself with search_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 provides no guidance on when to use this tool versus get_password or search_passwords, despite these siblings being present. While the parameter list implies filtering use cases, there is no explicit when/when-not guidance, leaving the agent to infer.

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