Get the BilkaToGo cart

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

The description adds substantial behavior beyond the annotations: prices are in DKK, the default and full return shapes, delivery availability semantics, personal-data redaction, login requirement, and a security warning about untrusted cart text. These details are consistent with readOnlyHint=true and openWorldHint=true.

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 front-loaded with the core action and then organizes return details, delivery semantics, privacy behavior, authentication, and safety guidance. Every sentence carries useful information, especially because there is no output schema.

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 fully explains what the tool returns in both compact and full modes. It also covers authentication, privacy redaction, delivery-slot semantics, and untrusted data handling, leaving no important gap for correct invocation.

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?

Although the schema fully documents the `full` boolean, the description adds real meaning by enumerating the compact fields returned by default and the extra fields `full` exposes, such as brand, size, aisle, availability, and distance from the minimum order.

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 and resource: read the cart on the user's BilkaToGo account. It clearly distinguishes reading from the sibling set_cart_* mutation tools by noting that reading changes nothing.

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 context is clear: use this to read the cart, with a default compact view and an optional full view. It does not explicitly name alternatives such as set_cart_quantity, but the read-versus-write distinction is made obvious.

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