List Folders

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

The description mentions 'safe folder id/name summaries only', reinforcing the readOnlyHint annotation. It does not contradict annotations and adds context about safety. No additional behavioral traits are needed for a simple list tool.

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, no wasted words. Information is front-loaded and every sentence contributes value.

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 is complete for a read-only list tool with two well-described parameters. It mentions return type (id/name summaries) despite no output schema. No gaps identified.

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%, so the description does not need to add parameter info. It doesn't provide extra meaning beyond the schema descriptions, which are adequate.

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 'List', the resource 'personal Bitwarden folders', and the scope 'visible to the current user'. It also specifies the purpose 'discover folder ids for item organization', which distinguishes it from sibling tools like keychain_get_folder.

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 explicitly says 'Use this to discover folder ids for item organization', indicating when to use it. The context of sibling tools implies when not to use. However, it lacks explicit exclusions or alternative tool mentions.

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