delete_webhook

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

With no annotations, the description carries the full burden. It clearly labels the operation as destructive, which is a critical behavioral trait. However, it does not disclose other aspects such as permissions required, reversibility, or side effects on dependent data.

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: a single sentence plus a prominent warning emoji. It is front-loaded with the critical caution and leaves no unnecessary words.

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 deletion tool with no output schema, the description covers the essential: what it does, that it's destructive, and the parameters are fully documented. It could mention the success state or error handling, but the warning and the schema_file confirmation compensate.

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 100%, so the schema already explains both parameters. The description adds only a generic 'with a given identifier' for webhook_id, which is already documented. The schema_file parameter is more detailed in the schema itself. Thus minimal added value beyond schema.

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?

Clearly states 'delete an existing webhook', which is a specific verb and resource. It distinguishes itself from sibling tools like modify_webhook and test_webhook, and the warning emphasizes its destructive nature.

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?

Explicitly warns 'Confirm with user before calling' and includes a required schema_file parameter that enforces a confirmation step. Lacks explicit alternatives or when-not-to-use scenarios, but the destructive directive suffices for safety.

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