gitea_delete_webhook

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

No annotations provided, so description carries full disclosure burden. Beyond the verb 'Delete', it reveals no behavioral traits: permanence, side effects on repository events, error conditions, or rate limits. For a destructive operation, this is insufficient.

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?

Extremely concise single sentence with no wasted words. However, given the lack of schema coverage and annotations, this brevity represents under-specification rather than effective distillation.

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?

Inadequate for a 4-parameter destructive operation with no output schema. Missing: parameter semantics, success/failure indicators, and whether deletion is immediate or queued. The agent lacks sufficient context to invoke this tool correctly without guessing parameter formats.

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 0% with no parameter descriptions. The description fails to compensate by explaining critical parameters like webhook_id (where to obtain it) or site (Gitea instance URL). 'From a repository' loosely implies owner/repo but doesn't document the actual parameter structure.

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') and resource ('webhook from a repository'), distinguishing it from sibling operations like gitea_create_webhook or gitea_test_webhook. The '[UNIFIED]' prefix is metadata noise but doesn't obscure the core purpose.

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 guidance provided on when to use this versus alternatives, nor prerequisites like obtaining the webhook_id from gitea_list_webhooks first. No warning about permanent deletion or impact on active integrations.

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