taiga_webhooks_delete

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

With no annotations, the description carries the full burden of behavioral disclosure. The word 'delete' implies destructive action, but the description does not state that deletion is permanent, whether associated webhook logs are affected, or if special permissions are required.

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 a single succinct sentence, 'Delete a webhook.', that is front-loaded and free of unnecessary words. For a tool with one clear parameter, this is appropriately concise.

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 one-parameter delete operation, the description plus schema is minimally viable. However, it lacks any mention of irreversibility, side effects on webhook logs, or what a successful response looks like, which would be valuable for an agent.

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?

The input schema fully documents the single parameter 'id' as 'Webhook ID' and marks it as required. The description adds no additional parameter meaning, so the baseline of 3 for high schema coverage is appropriate.

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 'Delete a webhook' uses a specific verb and resource, and clearly differentiates from sibling webhook operations like list, create, get, update, and test. However, it is essentially a restatement of the tool name and adds no context about what a Taiga webhook is.

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 is provided on when to use this tool versus alternatives, such as webhooks_update or disabling a webhook. There are no prerequisites, permission requirements, or consequences mentioned, leaving the agent without situational cues.

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