Add webhook

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

The openWorldHint annotation signals side effects, but the description adds no behavioral context beyond 'Create a webhook.' It does not disclose idempotency, duplicate behavior, or what happens after successful creation.

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?

Two concise sentences with no filler. The first sentence states the primary action, and the second directs attention to the key parameters. Every sentence earns its place.

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 simple 2-parameter creation tool, this covers the basics. However, without an output schema, it would benefit from describing expected response or post-condition behavior. The description is adequate but minimal.

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 descriptions cover both parameters at 100%, so the baseline is 3. The description adds value by giving concrete event examples (add_lead, update_contact), which clarifies the expected format beyond the schema.

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 states 'Create a webhook' with a specific verb and resource, and adds examples of events. This clearly distinguishes it from sibling tools like kommo_webhooks_list and kommo_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 implies usage for creating webhooks but provides no explicit guidance on when to use this tool instead of alternatives. It does not mention exclusions or prerequisites.

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