web_get_order

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

No annotations are provided, so the description carries the burden of explaining behavior. It does state what is retrieved and the quantity semantics, but it does not disclose anything about authentication requirements, error behavior, or whether the operation is read-only beyond the verb 'abrufen'.

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 compact sentence that front-loads the action and resource, with a parenthetical clarifying the returned quantities. Every word earns its place; 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 single-parameter read tool with an output schema, the description is largely sufficient: it identifies the exact resource and the key data returned. It could be slightly stronger by explicitly noting that it retrieves data for one order rather than a list, but the phrase 'einer einzelnen Bestellung' already conveys this.

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 only parameter is order_number. The description implies that this parameter identifies the single order whose positions are returned, adding some context beyond the bare schema, but it does not elaborate on format or required value semantics.

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 uses a specific verb ('abrufen') and a clear resource ('Positionen einer einzelnen Bestellung'), and clarifies the returned data as ordered/delivered quantity per article. It clearly distinguishes from the sibling web_get_order_list, which is about orders rather than individual order positions.

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 makes it clear this tool is for retrieving line items of one specific order, so an agent can infer it should be used when an order number is known. However, it does not explicitly mention when not to use it or point to a sibling alternative such as web_get_order_list for listing orders.

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