pipedrive_persons_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 usefully discloses the confirmation gate and the dry_run preview mechanism, which signals a guarded destructive operation. It does not, however, state that deletion is permanent/irreversible, nor whether linked records (deals, activities) are affected.

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 terse sentences with zero filler, front-loaded with the core action. Every sentence adds a distinct, actionable fact (what, confirmation, preview mode).

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 is workable but thin: it omits irreversibility, side effects on related entities, and expected return/preview shape. The 100% schema coverage compensates for parameter detail but not for the missing destructive-operation context.

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 are already documented in the schema, making the baseline 3. The description's mentions of confirm and dry_run merely restate what the schema already declares, adding no syntax or semantic 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 (Delete) and resource (a person), which unambiguously separates it from siblings like pipedrive_persons_update, pipedrive_persons_merge, and pipedrive_persons_get. No ambiguity about what the tool accomplishes.

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 conveys the invocation prerequisite (confirm must equal "DELETE") and that a dry_run mode exists, which is useful context. However, it gives no guidance on when to prefer this over alternatives such as merging duplicates (persons_merge) or deactivating via update, so usage is only implied.

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