Get an item

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value beyond them by disclosing the breadth of the response, including derived content (what the vision model read in photos) and unconfirmed state ('suggested fields waiting for the person to confirm'), which an agent needs to interpret results. It does not mention pagination or size limits, but for a single-item read that is minor.

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?

Front-loaded with the core statement, then a second sentence that handles routing to alternatives. Dense but every clause carries information; the enumeration of payload types is long yet each item is distinct.

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?

There is no output schema, so the description has to convey return values, and it does so thoroughly, including derived vision-model text and pending suggestions that would otherwise surprise an agent. For a one-parameter read-only tool this leaves nothing essential unspecified.

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 description coverage is 100% and there is only one parameter, whose provenance ('from search_inventory or list_items') is already stated in the schema. The description implies a single-item scope but adds no format or constraint detail beyond the schema, so baseline 3 applies.

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?

Names a specific verb and resource ('Everything about one item') and then enumerates the payload: fields, storage location and box, warranties and claims, photos/documents with vision-model extraction, and pending suggested fields. That distinguishes it clearly from item_history and list_items without opening either schema.

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?

Gives an explicit entry condition ('after search_inventory or list_items has found the item, when you need the details') and names two alternatives with the conditions that select them: item_history for change over time, list_items for a quick scan of many items.

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