view_cart

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

With no annotations, the description carries the full disclosure burden. The field list implies a read-only operation, but it never says so explicitly, and it omits behavior for an empty cart, currency/rounding of totals, or whether cagnotte values are live or cached.

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?

One sentence, front-loaded with 'Contenu du panier' before the field enumeration. The inline field list is dense but every item maps to a value the agent will receive.

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?

There is no output schema, so the description must describe the return value, and it does this thoroughly, including the meaning of cagnotte_total_eur. Without annotations it could say more about read-only safety and empty-cart behavior, but for a zero-parameter read tool this is close to sufficient.

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, so there is nothing for the description to compensate for; the baseline of 4 applies. The parenthetical field list documents the return shape instead, which is supplementary rather than 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?

States it returns the cart contents and enumerates the returned fields, which lets an agent distinguish this read operation from mutating siblings like update_cart_line and remove_from_cart. It never uses an explicit verb such as 'view/read/return', so the purpose is inferred from the field list rather than stated outright.

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?

Gives no guidance on when to call this versus add_to_cart, update_cart_line, or checkout_link, and no precondition such as requiring a cart session or authentication. Usage is only implied by the field listing.

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