Product View

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

With no annotations provided, the description carries the transparency burden. It discloses what is displayed (image, name, price, stock status, description) but does not mention side effects, required permissions, or behavior on invalid product IDs. It is adequate but not rich in behavioral detail.

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 three sentences, front-loaded with the core purpose, then a list of displayed fields, and finally usage guidance. Every sentence adds value, and there is no redundancy or filler.

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 display tool with two parameters and no output schema, the description covers the primary purpose, displayed fields, and typical usage flow. It is missing an explanation of the lang parameter and any mention of return format, but given the low complexity these are minor gaps.

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 only 50% (only product_id has a description). The description adds some context for product_id by linking it to list_shop_products, but it does not explain the lang parameter, whose schema entry has no description. Since the description fails to compensate for the undocumented lang parameter and does not clarify how parameters affect output, the value added is limited.

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 states a specific verb and resource ('Show a product detail page for a konsum.aare.guru merchandise item') and enumerates displayed fields. It is clear about what the tool does, though it does not explicitly differentiate from the sibling tool get_shop_product, which may serve a similar purpose.

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 provides explicit usage context: 'Use after list_shop_products to let the user inspect a specific item before adding it to their cart.' This tells the agent when to use the tool, but it does not mention alternatives or when not to use it, such as when raw product data is needed instead of a rendered page.

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