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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not say whether the operation is read-only, whether authentication or special permissions are required, how pagination behaves, or what the response shape looks like beyond the name implying retrieval.

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 short sentences, front-loaded with the core purpose and followed by useful usage context. There is no filler, repetition, or unnecessary exposition.

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 simple list/filter tool with 100% schema coverage and no output schema, the description gives enough to understand the resource and typical use cases. It omits any explicit read-only or pagination note, but the schema covers pagination and the list semantics imply read behavior.

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 documents all four parameters including filters and pagination. The description mentions buyer, supplier, and drop as filter dimensions but adds no syntax, format, or combination semantics beyond what the schema provides, making the baseline of 3 appropriate.

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 a specific verb ('Lists') and resource ('shopping carts'), and adds filtering scope. It does not explicitly distinguish itself from the sibling getCart, which retrieves a single cart, so it falls short of the top score for sibling differentiation.

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 clear usage contexts: finding specific carts by buyer, supplier, or drop, and browsing recent cart activity. It does not state when not to use it or name getCart as the alternative for single-cart lookups, but the context is clear enough to guide selection.

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