⚠️ Stock: update

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

Annotations already indicate destructiveHint: true and readOnlyHint: false. Description adds behavioral context: 'Affects whether listings are available to order: quantity=0 marks a listing as out of stock.' Explains consequence of setting quantity to 0. No contradiction with 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?

Two sentences plus two short clarifications. Front-loaded with key action and effect. No unnecessary words. Perfectly concise.

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?

Tool has no output schema, but description mentions 'Returns success and errors for each listing.' Covers main parameters. Could detail idempotencyKey/dryRun but schema does. Adequate for a destructive mutation with 3 parameters and no nested objects.

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. Description adds minimal value beyond schema: summarizes parameters (item_id, quantity, external_id?) and constraint (quantity 0..999999). Reinforces quantity=0 meaning but schema already describes it.

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?

Description clearly states 'Updates the stock (quantity) of items across listings in the warehouse.' Verb 'updates' plus resource 'stock' and scope 'items across listings' make purpose explicit. Distinguishes from sibling tool stock_get_stocks_info by explicitly referencing it for current stock.

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?

Explicitly states when to use alternative: 'For current stock, use stock_get_stocks_info.' Also implies use for setting stock levels and explains effect of quantity=0. No explicit when-not-to-use, but guidance is strong.

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