rami_levy_view_cart

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

With no annotations present, the description fully carries the behavioral burden. It reveals that the tool makes no network call, reads only local state, and cannot see website-side cart mutations. It also clarifies the checkout URL behavior on the Rami Levy site, providing substantial transparency for a stateful cart tool.

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 primary purpose and then adds crucial caveats and user-facing guidance. Every sentence earns its place: purpose, scope limitation, and checkout URL behavior. There is no filler or redundant detail.

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 no-parameter, no-output-schema tool, this description is unusually complete. It tells the agent what the tool returns, what state it operates on, what it cannot see, and what to communicate to the user. The only minor ambiguity is the reference to 'scope', but this does not undermine practical 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?

There are zero parameters, so the empty input schema fully covers parameter needs. The baseline for 0-parameter tools is 4, and the description adds no unnecessary parameter information while still providing relevant context about the tool's local scope.

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 ('Show'), a precise resource (this tool's own cart list since the last checkout), and the key outputs (running total, checkout URL). It also explicitly distinguishes itself from a read of the Rami Levy website cart, making its purpose unambiguous and differentiated.

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 gives clear context for when to use the tool: it reads local state only and is not a website-cart read. It clearly explains the limitation that website-side changes are invisible, but it does not explicitly name alternative tools or say 'use X instead' in this situation.

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