Get Item

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

The description reveals that secret fields and signed attachment URLs are redacted by default, and that reveal=true can override but may be forced false by NOREVEAL. This adds valuable behavioral context beyond the readOnlyHint annotation.

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, front-loads the main purpose, and every word adds value without repetition.

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 the readOnlyHint annotation and clear parameter descriptions, the description adequately covers the tool's behavior. No output schema exists, but the redaction behavior is explained.

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%, baseline 3. The description enriches both parameters: id is described as 'Stable Bitwarden object id returned by list/search/get/create tools', and reveal explains default behavior and potential override, adding nuance.

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', specifying the verb, resource, and identifier. It distinguishes itself from sibling tools like keychain_get_username, keychain_get_password by focusing on the full item retrieval.

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 mentions using 'stable item id' and instructs when to pass 'reveal=true' (only when caller is allowed secrets), but does not explicitly mention when not to use or compare with alternatives.

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