Remove from basket

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

No annotations are provided, so the description carries the full burden. It states the action but discloses no side effects, prerequisites, or response behavior. The agent is left uninformed about error states or confirmation requirements.

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 consists of two short, direct sentences with no redundancy. However, it could be more structured by including key parameter hints without adding much length.

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 tool with 4 parameters, no schema coverage, and no output schema, the description fails to provide essential invocation context. The agent cannot reliably construct correct calls without guessing parameter roles.

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%, yet the description provides zero information about the four parameters (store_id, product_id, store_product_id, basket_product_id). The agent cannot determine which parameter distinguishes the product to remove or that store_id is required.

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 explicitly states 'Remove one product from the real Glovo basket,' which clearly identifies the action (remove) and the resource (product from basket). This purpose is distinct from sibling tools like glovo_add_to_basket and glovo_get_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?

The instruction 'Do not call unless explicitly requested' provides a clear usage constraint, implying the tool should only be used when the user directly asks to remove a product. However, no alternatives or when-not-to-use scenarios are mentioned.

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