willys_get_product_detail

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the output is detailed product information and gives no insight into session/auth requirements, error behavior, response format, or side effects. The sessionId parameter is only visible in the schema, not explained.

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 a single concise sentence with no filler, front-loading the core purpose. It loses one point because it omits necessary context, but it is appropriately short and to the point.

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 there is no output schema and no annotations, this description is too sparse for an agent to understand what product details are returned, why sessionId is needed, or how this tool relates to siblings. It covers only the basic purpose and one parameter, leaving significant 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 description coverage is 0%, and the description only clarifies that 'artikelkod' corresponds to productCode. It does not explain sessionId at all, nor does it provide any format or constraint details beyond the schema's type declarations. The description adds minimal semantic value.

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 'Detaljerad produktinformation för en artikelkod' clearly communicates that the tool returns detailed product information for an article code, which distinguishes it from sibling tools like search or order details. It lacks an explicit verb, but the tool name supplies that, and the resource and scope are clear.

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 that the tool should be used when an article code is known and detailed product information is needed, which provides a basic usage context. However, it does not explicitly mention alternatives or when not to use it, such as when using willys_search for broad queries.

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