list_passwords

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

Annotations already declare readOnlyHint=true, so the description adds value by stating the secret value is never included and that only metadata fields are returned. This is beyond the annotation and clarifies the tool's non-destructive, metadata-only nature. No contradiction.

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 sentences: the first states the main purpose and scope, the second adds the critical caveat about secret exclusion and the optional filter. Every sentence carries meaningful information, with the most important detail (metadata only) front-loaded.

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 read-only list tool with one optional parameter and no output schema, the description covers the return fields, the exclusion of secrets, the pointer to get_password for secret retrieval, and the optional filter. An agent has enough information to decide when to use this tool and how to call it correctly.

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 parameter 'folder' is fully described in the schema as 'Optional folder id to filter by.' The tool description repeats the same optional filtering concept without adding syntax or format details. Since schema coverage is 100%, the description adds no extra parameter semantics beyond a restatement.

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 states a specific verb (list), resource (saved passwords), and clarifies the metadata-only scope, naming the exact fields returned. It also distinguishes itself from get_password by explicitly stating the secret is never included. This clearly separates it from sibling tools like search_passwords and get_password.

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 says to use get_password with a specific id to reveal a secret, giving clear direction on when to switch to an alternative. It also mentions optional folder filtering, but does not explicitly discuss when to prefer search_passwords over list_passwords. The context is clear for the core use case.

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