set_deck_card_quantity

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

With no annotations, the description explains absolute setting, removal on zero, and API key requirement. It could mention whether existing rows are overwritten or created, but overall provides key behavioral context.

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?

Three sentences cover action, edge case, alternative, and requirement. No wasted words, all information is essential.

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 four required parameters, no output schema, and no annotations, the description is complete enough. It covers core functionality, alternative tool, and a prerequisite. Could mention behavior for non-existent cards, but schema constraints mitigate risk.

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 coverage is 100%, so baseline is 3. The description adds value by clarifying that quantity is absolute and zero removes the row, which complements the schema's description of parameters.

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 sets the absolute quantity for a card and board in a deck, explicitly contrasting with delta operations. It specifies that a quantity of 0 removes the row, and distinguishes itself from the sibling add_deck_card.

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 directly tells when to use this tool (for absolute setting) and when to use an alternative (add_deck_card for incrementing). It also notes the requirement of an API key.

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