pipedrive_organizations_delete

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

No annotations are provided, so the description carries the burden. It usefully surfaces the 'confirm: DELETE' safety gate and the dry_run preview path, but says nothing about irreversibility, cascade effects on related records, or permission requirements for a destructive operation. Adequate but leaves meaningful behavioral 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?

Three short sentences, front-loaded with the core action and the hard requirement. Minimal waste, though the confirm/dry_run notes largely restate the schema.

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, an agent needs more: whether the delete is reversible, what happens to associated entities, and what errors to expect. The description covers the mechanics but not the consequences.

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 all four parameters (org_id, reason, confirm, dry_run) are already documented in the schema. The description repeats the confirm and dry_run semantics without adding format or edge-case detail, so the 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 an organization') that clearly distinguishes it from siblings like organizations_update, organizations_merge, or organizations_get. It lacks an explicit contrast to those alternatives, but the deletion intent is unambiguous.

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 gives no guidance on when to delete versus merging, archiving, or updating a record, and no warnings about prerequisites (e.g., linked deals/persons). The procedural note about confirm and dry_run is a gate, not usage guidance.

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