pipedrive_products_delete

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

No annotations are provided, so the description must carry the burden. It mentions required confirmation via the 'confirm' parameter and dry_run support, adding context beyond the schema. However, it does not disclose irreversibility, permission needs, or effects on related data.

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, highly concise, with no wasted words. Essential information is front-loaded, and the structure is clear.

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?

Given 4 parameters, no output schema, and no annotations, the description lacks explanation for the 'reason' parameter, does not specify return values or error behavior, and does not clarify if the tool is idempotent or safe to retry.

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 50% (descriptions for product_id and confirm). The description adds context for dry_run ('Supports dry_run') but ignores the 'reason' parameter entirely. It repeats the confirm constraint, adding minimal value beyond the schema.

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 'Delete a product,' specifying the verb and resource. It distinguishes from sibling tools like create, update, and list, and includes key constraints (confirm and dry_run).

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 description implies when to use (to delete a product) but provides no explicit guidance on when not to use or alternatives. It does not differentiate from other delete tools for different entities, though context makes it clear.

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