pipedrive_products_delete

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

With no annotations, the description carries the full behavioral burden. It does disclose two genuinely useful traits — a hard confirmation gate ("DELETE") and dry_run support for previewing — which go beyond the schema's raw fields. It omits the most important trait for a destructive tool: that the deletion is irreversible and what side effects it has on related records.

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 sentences, front-loaded with the action, then the safety gate, then the escape hatch. No filler. It is slightly too terse for a destructive operation, but nothing is wasted.

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 tool with no annotations and no output schema, the definition covers the confirmation and preview mechanics but not irreversibility, permission requirements, or the response shape on success/failure. Adequate minimum, with clear gaps an agent would want closed before calling.

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 the schema already documents all four parameters including confirm's exact value and dry_run's semantics. The description repeats confirm and dry_run rather than adding meaning, and never mentions reason or product_id. Baseline 3 applies.

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 ("Delete a product") that is unambiguous against create/update siblings. However, the catalog contains several delete tools for product-adjacent resources (pipedrive_product_variations_delete, pipedrive_deal_products_delete), and the description does not distinguish deleting a product record from deleting those, leaving a small routing gap.

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?

No when-to-use or when-not-to-use guidance, no mention of prerequisites (e.g. products still referenced by deals), and no naming of alternatives. The only conditional content is the confirm gate, which is an invocation requirement rather than usage guidance.

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