willys_get_order_details

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

With no annotations, the description carries the full burden for behavioral disclosure. It does specify the exact content ('alla varurader' = all product rows) which adds value, but it does not mention session/auth requirements, side effects, or error behavior, leaving gaps.

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, short sentence and is front-loaded, but it is under-specified. It earns its place in terms of brevity, yet the extreme brevity sacrifices necessary context.

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 read operation with two string parameters and no output schema, the description should at least clarify that orderId likely comes from willys_get_orders and that a valid sessionId is required. This is absent, making the tool's context incomplete.

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 does not explain what orderId or sessionId mean or how they are used. The only indirect reference is to 'a previous order', but the parameters are otherwise undocumented.

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 that the tool returns all product rows from a previous order, which clearly identifies the data scope. It distinguishes from list-order tools by focusing on order items, though it lacks an explicit verb like 'get' or 'retrieve'.

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?

No guidance is given on when to use this tool versus alternatives like willys_get_orders, nor any prerequisites such as obtaining an orderId from a prior call. The implied usage is retrieving details for a known prior order, but this is not made explicit.

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