keel_delete_webhook

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

With no annotations provided, the description carries the behavioral transparency burden. It discloses a non-obvious idempotency behavior: deleting a non-existent id still succeeds, so success does not prove removal. This is valuable context beyond what the schema shows, though it does not cover auth or side effects.

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 two sentences with no wasted words. The core action is front-loaded, and the critical idempotency caveat plus verification step are presented compactly in the second sentence.

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 single-parameter delete operation with no output schema, the description is complete enough. It explains the action, the surprising success semantics, and how to confirm the outcome, covering everything an agent needs to invoke and verify the call.

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?

The input schema already documents the only parameter, id, as 'The webhook subscription id to remove' with 100% coverage. The description's 'by id' adds little beyond the schema, so baseline 3 is appropriate.

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 uses a specific verb and resource: 'Delete a webhook subscription by id.' It is unambiguous and clearly distinguishes this tool from siblings like keel_create_webhook and keel_list_webhooks.

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 gives actionable guidance by warning that a success result does not confirm deletion and explicitly recommends calling keel_list_webhooks to verify. It does not explicitly list when not to use the tool, but the single-purpose delete operation makes that less critical.

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