Get Folder

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

Annotations declare readOnlyHint=true, and the description adds 'returns safe folder metadata only', reinforcing the read-only, non-destructive nature. No contradictions; the description provides context beyond what annotations give.

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 pack all needed information without wasted words. The description is front-loaded with the core action and then adds usage context.

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 tool with one parameter, no output schema, and clear annotations, the description is fully sufficient. It covers purpose, usage guidance, and safety, leaving no gaps.

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 and describes the 'id' parameter as 'Stable Bitwarden object id'. The description adds no further semantic meaning (only 'by stable folder id'), so baseline 3 is appropriate.

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 retrieves one personal Bitwarden folder by stable ID, and differentiates from sibling tools like keychain_list_folders (lists all) and keychain_get_item (gets items). It uses a specific verb ('get') and resource ('folder'), making the purpose explicit.

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 advises using this tool to verify a folder ID before updates, providing a concrete use case. However, it does not explicitly mention when not to use it or suggest alternatives, though the context of 'personal folder' and 'verification' implies limited scope.

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