pipedrive_webhooks_create

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

With no annotations, the description must disclose behavioral traits. It mentions that confirm must be 'YES' and supports dry_run, but fails to cover important behaviors like event delivery, authentication, rate limits, or what happens upon creation. This is insufficient for a 9-parameter mutation tool.

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?

The description is extremely short (one sentence and two fragments), but under-specification is not conciseness. For a complex tool, more detail is needed to be helpful, making the description insufficiently sized.

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?

Given the tool's complexity (9 parameters, no output schema, no annotations), the description is incomplete. It lacks details on prerequisites, behavior of dry_run, error handling, return values, and integration with sibling tools.

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 44%, leaving several parameters undocumented. The description adds value by emphasizing the confirm requirement and dry_run support, partially compensating for gaps. However, it does not clarify the meaning of parameters like user_id, http_auth_user, or http_auth_password.

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?

The description clearly states 'Create a webhook subscription', specifying a verb and resource. It distinguishes from sibling tools (pipedrive_webhooks_delete, pipedrive_webhooks_list) by name, but the description itself does not explicitly differentiate from alternatives like 'pipedrive_webhooks_delete'.

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 provides no guidance on when to use this tool versus alternatives, such as delete or list. It does not mention prerequisites, permissions, or scenarios where dry_run is appropriate.

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