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

There are no annotations, so the description carries the full behavioral burden. The verb 'Read' plus 'contents and totals' clearly signals a non-mutating snapshot operation. It does not cover edge cases like missing carts, but for a simple getter this is adequate and contradicts nothing.

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, no filler. The first sentence immediately states the operation and object, and the second gives the use case. Every word earns its place.

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?

Purpose, usage, and return content ('contents and totals') are covered, and the tool is simple and read-only. However, parameter meanings are left to inference, and there is no guidance on error behavior or output shape beyond totals.

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 schema has 0% description coverage, and the description does not explain what site_slug or cart_id mean or how they relate to the cart. The parameter names are suggestive, but the description fails to compensate for the absent schema documentation.

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 opens with a specific verb and resource: 'Read the current Agent Checkout cart contents and totals.' This clearly distinguishes get_cart from siblings like create_cart, add_to_cart, and get_product. The qualifier 'current' adds useful scope.

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 second sentence explicitly states when to use the tool: 'Use to review or confirm the cart before handing the buyer off to checkout.' This gives a clear usage context, though it does not mention exclusions or name alternatives such as create_cart.

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