Get Item

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

The description discloses that secret fields and signed attachment URLs are redacted by default, and that the 'reveal' parameter can override this with a permission constraint. It also mentions 'NOREVEAL' can force false. This adds significant context beyond the annotations, which only indicate readOnlyHint=true.

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 consists of two concise, front-loaded sentences with no extraneous information. Every word adds 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?

Given no output schema, the description mentions 'full vault item' but does not detail the structure or fields returned. It covers the key behavioral aspects (redaction, reveal) and parameter usage, but lacks explicit return value documentation.

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% description coverage, but the description adds meaningful context: for 'id', it specifies 'stable Bitwarden object id'; for 'reveal', it adds permission semantics (only when allowed). This goes beyond the schema's basic descriptions.

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 'Get the full vault item by stable item id.' It uses a specific verb (get) and resource (vault item by ID), distinguishing it from sibling tools like keychain_search_items which search by query.

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 explains when to use the 'reveal' parameter, stating it should only be set to true when the caller is allowed secrets. However, it does not explicitly contrast with alternatives or state when not to use this tool over other retrieval tools.

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