item_get

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

No annotations provided, so description carries full burden. It discloses that concealed field values are hidden unless 'reveal' is true, and that secretReference overrides vaultId/itemId. Lacks mention of permissions or error conditions, but covers core behaviors.

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 front-load the main purpose and then provide key details. No extraneous information; every sentence earns its place.

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 tool's simplicity and clear parameter definitions, the description sufficiently covers what is retrieved and how to use it. No output schema needed; users understand the return structure from description.

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?

All 4 parameters are described in schema (100% coverage). Description adds value by explaining secret reference format, the override behavior, and default for reveal. Goes beyond schema details.

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 'Retrieve a full 1Password item' and lists included fields (title, category, tags, notes, fields). It distinguishes from sibling tools like item_archive, item_delete, item_edit, item_list, item_lookup, etc., which have different actions.

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?

Describes two input methods (secret reference or vault ID + item ID) with clear precedence. Does not explicitly state when to use this tool instead of alternatives like item_lookup for searching or item_list for listing, but the context is clear.

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