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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds value by enumerating what fields come back (useful since there is no output schema), but says nothing about missing-id behavior, location scoping effects, or response shape beyond the field list.

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 compact fragments, front-loaded with the core purpose and field list. The trailing endpoint reference ('GET /api/v2/item/{id}') is mildly redundant but cheap and aids API mapping.

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?

With no output schema, the field enumeration is a meaningful substitute for describing return values, and annotations carry the safety profile. Only minor gaps remain: error behavior for an unknown id and how the optional location parameter changes the response, the latter of which the schema already covers.

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%, and the schema already explains both the id source and the location-scoping semantics (quantities reflect that location). The description adds no parameter meaning beyond that, so the 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?

States a specific verb ('get') and resource ('one item by id'), then enumerates the returned fields (quantities, prices, accounts, vendor, category, units of measure, price tiers, custom fields). This implicitly distinguishes it from sosinventory_list_items and sosinventory_get_item_bom, though it doesn't name a sibling explicitly.

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?

Usage is only implied: the schema note 'from sosinventory_list_items' hints at the workflow, but the description itself says nothing about when to call this versus list_items, get_item_bom, or get_transaction. No exclusions or prerequisites are stated.

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