pipedrive_deal_products_delete

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

No annotations are provided, so the description carries the full disclosure burden. It does add value by flagging the mandatory confirmation string and dry_run preview, but says nothing about irreversibility, required permissions, or side effects (e.g., deal value recalculation) for a destructive mutation.

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 short, front-loaded fragments with no filler — the core action comes first, followed by the two operational caveats. Telegraphic style leaves no wasted words, though it is terse to the point of terseness rather than fully structured prose.

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 destructive mutation with no annotations and no output schema, the description covers the confirmation and preview mechanics but omits expected return behavior and the consequences of deletion. It is adequate but leaves meaningful gaps for a delete operation.

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 100%, so every parameter (confirm, dry_run, deal_id, deal_product_id, reason) is already documented in the schema. The description merely restates confirm and dry_run without adding syntax or format detail beyond 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?

States a specific verb and resource ('Remove a product from a deal'), which is unambiguous on its own. It doesn't explicitly differentiate from sibling pipedrive_deal_products_update, though the verb 'remove' naturally contrasts with add/update.

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 mention of 'Requires confirm: "DELETE"' and 'Supports dry_run' implies the intended workflow (confirm first, optionally preview), but there is no explicit when-to-use guidance or routing away from sibling tools like pipedrive_deal_products_update.

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