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

With no annotations provided, the description carries the burden of disclosing side effects. It explicitly states that 'All pending deliveries will be cancelled' and 'This action cannot be undone,' which are critical behavioral traits beyond a simple delete. This provides valuable context about irreversibility and impact on ongoing deliveries.

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 extremely concise, using only two sentences to convey the core action and key caveats. It is front-loaded with the main verb and includes only essential information without any filler.

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 delete operation with one parameter and no output schema, the description covers the essential aspects: what it does, the cancellation of pending deliveries, and irreversibility. It doesn't mention error handling or where to find the webhook_id, but these are not critical for this level of simplicity. Overall, it is sufficiently complete.

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 provides complete coverage for the single parameter webhook_id, with a clear description. The description adds no additional meaning or format details beyond the schema, so it provides minimal added value. Baseline score of 3 is appropriate given high schema coverage.

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 the tool's function with a specific verb and resource: 'Delete a webhook endpoint.' This distinguishes it from sibling tools like create_webhook and update_webhook. The purpose is immediately clear.

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 implies usage when a webhook needs to be removed, but does not explicitly state when to use it over alternatives or mention any prerequisites. It does not name alternative tools like update_webhook or provide exclusion criteria. Thus, usage is only implied.

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