Get product details

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds value by listing the data payload (ingredients, allergens, nutrition, storage, promotion, price), which tells an agent what it can answer after calling. No mention of error behavior, but the read-only nature plus the payload listing is sufficient.

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 tight sentences, front-loaded with the purpose and payload, followed by the id sourcing. Zero wasted clauses.

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?

There is no output schema, so enumerating the returned fields is exactly the compensating information needed. Combined with the explicit id-source chain, an agent can call this correctly with no further 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 description coverage is 100% and the single productId param has a pattern plus an example (s1004201). The description only repeats the sourcing of the id from search_products or get_cart, adding no syntax or format detail beyond the schema, so baseline 3 is appropriate.

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 opens with a specific verb+resource (get the details of a Picnic product) and enumerates the content returned – ingredients, allergens, nutrition, storage, promotion, price. That enumeration clearly separates it from siblings like search_products or get_cart, which return lists rather than a single product's full detail.

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?

It gives a concrete use case (questions such as whether a product contains gluten) and an explicit prerequisite chain: obtain the id from search_products or get_cart. The only gap is it doesn't state when-not-to-use or what happens if the id is invalid.

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