Get basket

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

No annotations are provided, so description carries full burden. It discloses read-only behavior and mentions authentication context ('authenticated Glovo basket'), but does not detail response format, error conditions, or side effects.

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 sentences, zero wasted words. The core action is front-loaded in the first sentence, and the conditional variation is efficiently stated in the second.

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 tool with one optional parameter, the description is adequate but incomplete: it lacks details about the response (basket contents, status) and does not mention error conditions (e.g., authentication failure, missing basket).

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 optional store_id parameter is explained: if provided, it reads a different store's basket. Schema coverage is 0%, so description adds crucial meaning beyond type constraints.

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?

Description clearly states it reads the current Glovo basket, with a conditional variant for a store-specific basket. The verb 'read' and resource 'basket' are specific, and it distinguishes from mutation siblings like glovo_add_to_basket.

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?

Description implies use for reading basket state, but does not explicitly advise when to use this versus alternative tools such as glovo_add_to_basket or glovo_remove_from_basket. No usage exclusions or prerequisites are stated.

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