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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that stock is included in the response and cites the underlying endpoint (GET /inventory/<ASSET#>), but says nothing about behavior on a missing/invalid asset number or about the shape of what comes back.

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 short fragments with zero padding, and the core purpose is front-loaded before the endpoint reference. The endpoint string is arguably filler since the agent cannot use it, but it costs little.

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 carries more burden than a thin read tool normally would; it only tells the agent that stock is included, not what other fields the item record contains (e.g., custom fields). Adequate to call correctly, but not fully informative about the result.

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%, so both asset_number and include_custom_fields are already documented in the schema. The description reinforces the item-number identifier but adds no meaning beyond the schema, and it never mentions the custom-fields flag.

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 and resource: retrieves a single inventory item by item number, including its stock. This distinguishes it from list_inventory and search_inventory, though it doesn't differentiate itself from get_asset or get_asset_stock, which sound like near-neighbors.

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?

There is no guidance on when to use this instead of list_inventory, search_inventory, get_asset, or get_asset_stock. The agent must infer the selection rule purely from the tool name and the one-line purpose.

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