pipedrive_deals_delete

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

No annotations are provided, so the description carries the full burden. It discloses the confirmation requirement and dry_run preview behavior, which is useful. But it doesn't state whether deletion is permanent or reversible, what permissions are required, or what happens to associated entities (activities, notes, products). For a destructive operation, these are meaningful gaps.

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 short sentences, no wasted words, front-loads the action and the required confirmation. Highly efficient.

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 description is too thin. It omits critical behavioral facts: permanence, required permissions, side effects on related records, and whether dry_run returns output schema information. The confirmation mechanism is covered, but the overall picture is incomplete.

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 the schema already documents all four parameters (deal_id, confirm, dry_run, reason). The description adds a high-level summary but doesn't provide additional meaning beyond what the schema already conveys. Baseline 3 is appropriate when the schema fully documents parameters.

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 (Delete) and resource (a deal), immediately distinguishing it from siblings like pipedrive_deals_get, pipedrive_deals_update, or pipedrive_deals_move_stage. No ambiguity about what the operation does.

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 explains the guardrails (confirm must equal "DELETE", dry_run available for preview), which implies when to use each mode. However, it doesn't mention alternatives (e.g., pipedrive_deals_update for archiving) or when deletion is preferable. Usage is implied rather than explicitly guided.

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