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

The annotations already declare readOnlyHint=true, so the description needs only to add context beyond that. It adds that abandoned carts are included and that filtering/sorting/expansion are supported, which are useful behavioral details not present in the annotation.

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 two sentences long, with no filler. The first sentence conveys the core functionality, and the second provides a precise API reference. Every word earns its place, and the key information is front-loaded.

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 list tool with five optional parameters and no output schema, the description gives a reasonable overview of scope and capabilities. It lacks explicit return format details, but given the simple resource-oriented nature and the schema coverage, it is complete enough for agent use.

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 100%, so the schema already fully describes all five parameters. The description's mention of 'filtering, sorting, and expansion' maps to the where, sort, and expand parameters but adds no new meaning beyond what the schema already states.

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 clearly states the tool lists shopping carts, explicitly including abandoned carts, with filtering, sorting, and expansion. This distinguishes it from sibling list tools that target other resources (orders, products, customers) and from single-resource get tools.

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 provides clear context that this is for listing carts, including the API endpoint. It does not explicitly mention when not to use it or alternatives like swell_query, but the resource-specific scope and capabilities are evident, giving the agent a solid basis for selection.

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