Gitea: Delete webhook

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the safety profile is covered. The description adds nothing beyond that — it does not say the deletion is irreversible, whether it requires repo admin permission, or what the result/error looks like on an unknown webhook_id.

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?

A single efficient, front-loaded sentence with zero waste — but that brevity is under-specification rather than disciplined concision, and the bracketed "[UNIFIED]" tag carries no informational value.

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?

With four required parameters at 0% schema coverage, a destructive annotation, and no output schema, the description should at minimum explain the site parameter and the irreversibility of the operation. As written it is too thin for the tool's complexity.

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 0% for all 4 required parameters, so the description must carry weight. It implies owner/repo/webhook_id semantics via "webhook from a repository," but says nothing about the "site" parameter (multi-instance selector) or id format, leaving a meaningful gap.

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+resource: "Delete a webhook from a repository." The prefix "[UNIFIED]" is unexplained noise, but the operation is unambiguous and tellable apart from gitea_create_webhook, gitea_get_webhook, and gitea_update_webhook by name alone.

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?

No when-to-use guidance, no prerequisites (admin/ownership rights), and no warning that deletion is permanent or how to recover/verify. The agent must infer everything about when this is the right call versus gitea_update_webhook or gitea_get_webhook.

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