pipedrive_webhooks_delete

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

With no annotations, the description must carry the behavioral burden. It does disclose two real traits — a confirm gate guarding the operation and a dry_run preview mode — which is meaningful. But it omits whether deletion is permanent/irreversible, permission requirements, and side effects, leaving significant gaps for a destructive mutation.

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, front-loaded with the core action and followed by the two operational constraints. No filler and no redundancy.

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?

With no annotations and no output schema, the description covers the key facts an agent needs (confirm gate, dry_run preview) but does not state irreversibility of the delete or error/permission behavior, leaving it only adequate for a destructive tool.

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. The description's mentions of confirm and dry_run merely restate schema fields without adding syntax, format, or interaction details, so 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?

"Delete a webhook" states a specific verb (Delete) and resource (webhook), and the verb distinguishes it from its siblings pipedrive_webhooks_create and pipedrive_webhooks_list without opening any schema.

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 states a usage precondition (confirm must be "YES") and a preview option (dry_run), which implies when it is safe to invoke. However, it gives no explicit when-to-use/when-not guidance and never references alternative sibling tools, so usage remains implied rather than directed.

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