pipedrive_webhooks_create

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

With no annotations, the description carries the full behavioral burden. It correctly signals a mutation ('Create'), flags a confirmation gate (confirm: "YES"), and notes a preview mode — useful safety context. But it omits permissions required, idempotency/duplicate handling, side effects, and what the confirmation protects against, so the disclosure is partial.

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. Nothing is padded or buried. The confirm sentence is somewhat redundant with the schema's const definition, keeping it from a 5.

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 9-parameter mutation tool with no annotations and no output schema, the description is thin: it says nothing about permissions, what the response contains, or how the created webhook behaves. The rich schema covers parameter semantics, but the behavioral wrapping an agent needs before firing a write is only partially present.

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%, including full enum documentation and descriptions for confirm, dry_run, and every other parameter, so the schema does the heavy lifting. The description restates confirm and dry_run without adding format, constraints, or guidance beyond what the schema already says — baseline 3.

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: 'Create a webhook subscription.' An agent can immediately tell this apart from pipedrive_webhooks_list and pipedrive_webhooks_delete. However, it never explicitly names those siblings or clarifies the scope of the created subscription, so it stops short of a 5.

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?

There is no when-to-use guidance relative to alternatives, and no conditions, prerequisites, or exclusions beyond the required confirm value. 'Supports dry_run' hints at a preview workflow but does not explain when to prefer dry_run over a live call.

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