get_product

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

No annotations are provided, so the description must cover behavior. It lists what is returned (price, brand, etc.), which is good. However, it does not mention error handling (e.g., if product not found) or authentication requirements. For a read-only fetch, the description is adequate but not rich.

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: first defines purpose and return fields; second provides usage context and example queries. No superfluous information.

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?

With no output schema, the description enumerates returned fields. It also mentions the prerequisite (search_products). Missing: error cases and authentication, but these are minor for a simple fetch. Overall, complete enough for effective use.

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%; both parameters have descriptions. The description adds context beyond the schema by explaining that 'id' is chain-specific and obtained via search_products, and reiterates the chain constraint.

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 ('Fetch full product details') and resource ('product for a specific chain + product ID pair'), and lists returned fields. It distinguishes from sibling 'search_products' by explaining that this tool is for drilling into a single result.

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?

Explicitly says 'Obtain product IDs from search_products' and 'Use for get details for this Migros product' or unit price queries. The sibling tools include search_products, making the workflow clear.

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