Get Jumbo Basket

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

Annotations already declare readOnlyHint=true, so the safety profile is covered by structured data. The description adds genuinely useful context beyond that: the exact returned fields and the backing GraphQL ActiveBasket operation, plus an explicit exclusion list of write/checkout/order/payment operations. It does not mention auth requirements, so it falls short of 5.

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: the resource and returned contents come first, then the scope exclusions. Every clause carries information and nothing is repeated 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?

With no output schema, the description compensates well by enumerating the returned fields and confirming the read-only, non-transactional nature of the call. The one omission is the prerequisite of an authenticated session, which matters given jumbo_login and other session-bound siblings exist.

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?

The tool takes zero parameters and the schema is an empty object at 100% coverage, so the baseline is 4. There is nothing parameter-related for the description to clarify, and it correctly does not invent any.

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 gives a specific verb ('Read-only view') and resource ('the current Jumbo basket'), and enumerates the payload (lines, quantity, unit price, line total, promotions, subtotal). It does not name a competing sibling, but no sibling in the list also returns the active basket, so the resource itself is differentiating.

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?

Usage is implied by 'current Jumbo basket' plus the negative scope ('No basket writes, no checkout, no order, no payment operations'), which tells the agent what this is not for. There is no explicit when-to-use statement or prerequisite (e.g. that a session from jumbo_login is required), and no alternative tool is named.

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