preview_mouser_cart_change

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description is consistent. It adds that the tool reads current cart state and computes an exact diff for various operations, reinforcing its non-mutating nature. No contradictions.

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 one concise sentence, front-loaded with the tool's primary function, and lists operations efficiently without redundancy.

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?

Given the tool's complexity (8 operation types, nested request object, no output schema), a one-sentence description is insufficient. It lacks parameter guidance and details about the diff output format, though the annotations and operation list provide some context. Overall, it's a functional but not comprehensive description.

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 single 'request' parameter is a complex nested object with multiple sub-fields, and the schema has zero descriptions. The description provides no guidance on how to structure the request, what each operation requires, or the relationship between fields. This is a significant gap; the description must compensate but does not.

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 uses specific verbs 'read' and 'preview' and enumerates the operation types (add, update, remove, replacement, order-copy, schedule). This clearly distinguishes it from 'execute_mouser_cart_change' which performs changes, and 'get_mouser_cart' which only reads state.

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 implies usage scenarios through the list of operations, but does not explicitly state when to use it versus alternatives like execute_mouser_cart_change. The context is clear enough: to preview a change before applying it. No explicit exclusions are mentioned.

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