get_inventory_product

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds useful behavioral context about duplicate handling and the ability to look up by ID or name, which goes beyond annotations. However, it doesn't describe return format or error conditions.

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, no fluff. The first sentence states the main purpose and lookup method; the second addresses edge case. Efficient and front-loaded.

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?

For a simple 'get one' tool, the description fully covers how to identify the product (ID or name, with category for duplicates). Output schema exists externally, so return value documentation is not needed. Complete and appropriate.

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% with minimal descriptions ('a string that will be trimmed'). The description adds meaning by explaining that 'product' can be an ID or exact name, and that 'category' is used for disambiguation. This provides context beyond the schema.

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 specifies the action 'Get one inventory product' and the resource 'inventory product'. It distinguishes from list tools by stating it retrieves a single product, and provides lookup methods (by ID or exact name).

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?

Explicit guidance is given for handling duplicate product names: 'pass category or use the product ID'. This indicates when to use the optional category parameter. It does not explicitly compare to sibling tools but context from tool name and sibling list tools makes it clear.

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