add_buy_list

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

No annotations provided, so description carries full burden. It discloses that the operation is a real write, increments quantity, and creates rows if absent. However, it does not mention error handling (e.g., invalid cardId) or return value, which would improve transparency.

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 sentences, front-loaded with action and behavior. No unnecessary words, every sentence adds value.

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?

Adequate for a simple tool with few parameters and no output schema. Missing information on return value and error scenarios, but core functionality and sibling differentiation are covered.

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%, baseline 3. Description adds behavioral context: 'incrementing the quantity' and 'creates the row if absent' explain the effect of parameters beyond type/format. Also notes defaults for isFoil and quantity.

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 action: adding a card to the buy-list with incrementing quantity and row creation if absent. It specifies the resource (authenticated user's buy-list) and distinguishes from siblings update_buy_list and remove_buy_list.

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?

Provides explicit alternatives (update_buy_list for absolute quantity, remove_buy_list for deletion) and notes API key requirement. Does not explicitly state when not to use this tool beyond alternatives, but context is clear.

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