get_product

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

No annotations are present, so the description carries the full burden. It discloses that the response includes variants, options, and images, which is useful. However, it does not mention error behavior, permissions, or that it is read-only (though the verb 'Get' implies no side effects). Sufficient for a simple read tool but could be richer.

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?

A single, clear sentence with no wasted words. The essential verb and resource are front-loaded, and the included related data is listed efficiently. Perfectly concise.

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 one-parameter read tool with no output schema, the description covers the main function and return contents. It does not explain return format or error cases, but with such a low complexity, it is mostly complete. Sibling tools like list_products are not referenced, but this is not critical for a basic get-by-ID operation.

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?

The input schema fully describes the only parameter, product_id, with 'Product ID (numeric). Required.' (100% coverage). The description 'by ID' adds no new meaning beyond the schema. Baseline of 3 is appropriate since schema does the heavy lifting.

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 'Get a single product by ID' with a specific verb and resource, and adds that it includes variants, options, and images. It distinguishes from list/search products, though it doesn't explicitly name alternatives like get_order. This is clear but not maximally differentiated.

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?

No guidance is provided on when to use this tool versus alternatives such as list_products or search_products. The description implies use when you have a specific product ID, but does not state exclusions or preferences. This is a clear gap.

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