webhooks_delete

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

With no annotations provided, the description carries full burden. It clearly discloses the permanent/hard-delete nature with no recovery ('hard delete with no recovery'), which is the critical behavioral trait for a deletion tool. It doesn't describe return values or auth requirements, but the core destructive behavior is well communicated.

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?

Two efficient sentences with zero waste. The first states the purpose and consequences, the second provides the alternative. Front-loaded with the most critical information (permanent deletion) at the start.

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 deletion tool with 100% schema coverage, this is complete. The irreversible nature is stated, an escape-hatch alternative is provided, and no output schema exists so nothing to document there. The complex destructive behavior is fully covered by the description.

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%, so the schema already documents both uuid and companyId params. The description adds no additional parameter-level detail beyond what the schema provides. Per the rubric, baseline 3 is appropriate when schema does the heavy lifting.

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 verb (delete), resource (webhook endpoint), and explicitly notes it permanently removes both the endpoint and its delivery history. It distinguishes from the sibling webhooks_update by noting that tool pauses deliveries temporarily, making the destructive nature 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?

The description explicitly states when to use this tool (permanent delete) versus when NOT to use it (pause deliveries), and names the exact alternative (webhooks_update with isActive: false). This is model guidance comparable to the HIGH calibration example.

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