get_product_details

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

Without annotations, the description carries the full burden. It discloses that the tool is read-only via the 'read' tag and warns that this local server is an introspection stub for a hosted endpoint, making the behavioral limitation clear. It does not detail auth or rate limits, but for a stub, the transparency is adequate.

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?

The description is extremely concise: two sentences (plus a tag) with no filler. It front-loads the read tag and key items, and every word serves a purpose.

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?

Given 7 optional parameters and no output schema, the description is too sparse. It does not explain how to use parameters like filters or limit, nor does it describe the return format. The stub warning is useful but leaves gaps for a production context.

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 all parameters described, so baseline is 3. The description adds no extra meaning beyond the schema, such as how to use start_date or end_date together, so no improvement over baseline.

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?

Description explicitly states it reads product info, images, dimensions and is tagged as '[Catalog / read]'. It clearly differentiates from sibling tools like get_order_details or get_inventory_health, which cover different domains.

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?

The description implies the tool is for product details but does not explicitly state when to use it over other get_ tools or when not to use it. The note about being a stub provides some context, but lacks direct comparison to alternatives.

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