deals_remove_product

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

Discloses that deal value updates automatically, which is a key side effect. However, with no annotations, the description should also cover idempotency, error conditions, or reversibility. The side effect is noted but additional behavioral details are missing.

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?

Description is concise with a clear structure: one-line summary, then bullet points for tips and use cases. Every sentence adds value 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?

For a simple removal operation, the description covers most aspects: purpose, prerequisites, and side effects. It does not mention the return value or response shape, but since no output schema is provided, this is a minor gap. Overall fairly complete.

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?

Input schema already has 100% description coverage for both parameters. The description adds value by clarifying that product_attachment_id is not product_id and providing example values, but this is incremental. Baseline 3 is appropriate.

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 removes a product from a deal, using specific verbs ('Remove', 'Detaches'). It distinguishes itself from siblings like deals_add_product and deals_update_product by focusing solely on removal.

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 concrete workflow tips: use deals/list_products to get product_attachment_id, notes it's different from product_id, and mentions automatic deal value update. Includes example JSON. Lacks explicit 'when not to use' guidance, but context is clear enough.

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