Delete a webhook subscription

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

The description contradicts the annotations: it calls the operation an 'idempotent soft delete,' but the annotations set idempotentHint=false. This is a direct annotation contradiction, so the score is capped at 1 regardless of the otherwise useful details about soft deletion, delivery history retention, and required scopes.

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 front-loaded with the purpose and key behavioral traits, then follows with operation metadata, scopes, and workspace guidance. It is mostly well structured, though the contradictory 'Does not require idempotency' line and some boilerplate metadata slightly reduce clarity.

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 that an output schema exists, the description need not explain return values, and it does cover auth scopes, data sensitivity, workspace overrides, and terminal soft-delete behavior. The idempotency contradiction is a notable flaw, but otherwise the description is fairly complete for a delete operation.

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 67%; the description adds meaningful context beyond the schema by stating that workspaceId or workspaceSlug override the default workspace configured by the environment. It also maps the id parameter through the DELETE /api/webhook-subscriptions/{id} operation.

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: 'Delete an outbound webhook subscription.' This clearly distinguishes it from sibling tools like luca_webhooks_subscriptions_list, create, and update.

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?

It provides implied usage context by stating the operation is terminal and the subscription can never be resurrected, which warns the agent to use it carefully. However, it does not explicitly state when to use this tool versus alternatives such as updating or disabling a subscription.

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