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

Annotations already declare destructiveHint=true, so the safety profile is covered. The description adds no behavioral context beyond that: it does not say whether deletion is permanent, what happens to delivery history or in-flight events, or whether any confirmation/retry semantics exist. The API route mapping (DELETE /management/webhooks/{id}) is documentation trivia rather than agent-relevant behavior.

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?

Very short and front-loaded: the verb and resource appear in the first three words. The second sentence restating the REST route is mildly redundant for an agent but costs little space.

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 single-parameter destructive delete with no output schema, the essentials are present and the destructiveHint annotation covers the risk. Missing is any statement of irreversibility or post-deletion state, which would matter most for a destructive 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 coverage is 100% and there is a single required parameter, so the schema already explains webhook_id fully. The description adds nothing about the identifier's format or where to obtain it, so the baseline 3 applies.

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?

States a specific verb (Remove) and resource (a webhook), which cleanly separates it from formbricks_create_webhook, formbricks_get_webhook, and formbricks_list_webhooks by name. It does not explicitly call out those siblings or the scope of removal, but the action is unambiguous.

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?

There is no when-to-use guidance, no prerequisite (e.g. that the webhook must be fetched first), and no alternative or exclusion stated. The agent must infer that this is the sibling to reach for when a webhook should be removed.

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