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

Annotations already disclose that this is a destructive, idempotent, open-world mutation. The description adds meaningful behavioral context by stating that an existing card's quantity is replaced by the given quantity, which clarifies the upsert-like semantics beyond the annotations.

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 tightly written sentences with no wasted text. The core operation is front-loaded, and the important replacement rule follows immediately.

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?

The description covers the main purpose and replacement semantics, and annotations already carry the mutation safety profile. Still, with low schema description coverage and no output schema, it leaves several invocation details and edge-case behaviors implicit.

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 only 33%, so the description partially compensates by naming product, finish, and language as the card identity and by explaining quantity replacement. However, it does not clarify listId, clientRequestId retry behavior, or optional item pricing/condition fields.

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 states a specific verb and resource: adding cards to a CardNexus list by product, finish, and language. It is clear enough to distinguish from adjacent tools like create_list or remove_list_item, though it does not explicitly name alternatives or scope boundaries.

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 explains the core operation and replacement behavior but gives no explicit guidance on when to use this tool versus siblings such as add_inventory_items, update_cart_item, or remove_list_item. Usage is only implied by the tool name and description.

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