Delimit Webhook Manage

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

The description discloses side effects per action: add/remove mutate ~/.delimit/webhooks.json, test sends a test notification, and list is read-only. This meaningfully supplements the annotations (readOnlyHint=false, destructiveHint=true) with operation-specific behavior and file-level impact.

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 well-organized into focused sections and front-loads the core purpose. There is minor redundancy between the 'When NOT to use' section and the 'Sibling contrast' paragraph, but overall every section earns its place and is easy to scan.

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 full parameter documentation in the schema, an output schema present, and annotations provided, the description covers what remains: when to use, when not to use, side effects, and sibling differentiation. An agent has everything needed to select and invoke this tool correctly.

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 coverage is 100%, so the input schema already documents url, action, and events. The description adds extra semantic value by tying actions to side effects and clarifying test behavior, which goes beyond a bare schema listing.

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 opens with a specific verb and resource ('Manage webhook notifications for governance events') and immediately clarifies what registering a Slack/Discord/HTTP webhook does. It explicitly contrasts itself with delimit_siem and delimit_notify, so an agent can distinguish this tool from siblings without inspecting schemas.

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?

Provides explicit 'When to use' and 'When NOT to use' guidance, naming the exact alternatives (delimit_siem for streaming, delimit_notify for one-shot notifications). This gives clear decision rules and removes ambiguity about selection.

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