gitflic_webhook_delete

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds essentially nothing beyond that: no confirmation of irreversibility, no error behavior for a missing uuid, no permission requirements, and no note about the 'raw' escape hatch it exposes.

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 front-loaded sentence with no filler; the verb and key parameter come first. It is efficient but borders on under-specified rather than genuinely tight.

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 destructive, open-world mutation with no output schema and an undocumented required 'project' parameter, the definition is thin – an agent could invoke it without knowing the project identifier format or the failure mode. The destructive/idempotent hints from annotations partially compensate, keeping this from being inadequate.

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 only 33% – only 'raw' is documented in the schema. The description clarifies that 'uuid' identifies the webhook being deleted, which is genuinely useful, but it says nothing about 'project' (owner/repo slug? numeric id?) or how the two required parameters combine to scope the target.

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 states a specific verb and resource ('Delete a webhook') plus the identifying key ('by uuid'), so an agent knows exactly what operation this is. It does not explicitly distinguish itself from siblings like gitflic_webhook_create or gitflic_webhook_get, but the delete verb makes the distinction largely self-evident.

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?

There is no guidance on when to reach for this tool versus alternatives, no precondition such as needing an existing webhook uuid (retrievable via gitflic_webhook_list/get), and no mention of what happens if the uuid is wrong. The agent must infer all usage context.

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