delimit_webhook_manage

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

Discloses side effects: action='add'/'remove' mutate ~/.delimit/webhooks.json, action='test' sends test notification, action='list' is read-only. Without annotations, this provides necessary behavioral context. Could mention persistence or reversibility, but still strong.

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?

Well-structured with clear sections (When to use, When NOT to use, Sibling contrast, Side effects) in a concise format. Every sentence adds value, no repetition.

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?

Covers all key aspects: governance alerts, mutation, test functionality, file path. Given 3 parameters with 100% schema coverage and output schema present, the description is complete and self-contained.

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%, baseline 3. Description adds meaning: explains action parameter's effects (mutate vs test vs read-only), clarifies url requirements for add/remove/test, and events filter values. Adds value beyond 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 clearly states it manages webhook notifications for governance events, using a specific verb (manage) and resource (webhook). It contrasts with sibling tools delimit_siem and delimit_notify, distinguishing itself from structured streaming and one-shot notifications.

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?

Explicitly says when to use (register a Slack/Discord/HTTP webhook for governance alerts) and when NOT to use (SIEM-class streaming or one-shot notifications), naming specific alternatives. Also provides sibling contrast.

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