kaiten_delete_webhook

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

With no annotations, the description carries the full behavioral disclosure burden. It does disclose a key behavioral trait: DELETE may return 405 and removal may not be supported via the API. However, it does not mention permissions, idempotency, or success/error response behavior beyond the HTTP status warning.

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 two sentences with no filler. The primary action is front-loaded, and the important caveat immediately follows, making the most critical behavioral information easy to notice.

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 two-parameter delete operation, the description includes the critical unsupported-API caveat and clarifies the resource type as external. It omits return/output details, but no output schema exists and the action is straightforward; a brief note about expected success behavior would make it fully complete.

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 documents both parameters. The description adds the 'external webhook' resource qualifier, but does not provide additional meaning about the space_id or webhook_id values beyond what the schema states.

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 an external webhook from a Kaiten space.' The qualifier 'external' distinguishes it from sibling tools like kaiten_delete_incoming_webhook, and the caveat about API support does not 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?

The description provides no guidance on when to use this tool versus alternatives such as kaiten_delete_incoming_webhook or kaiten_list_webhooks. The only context is a limitation note, not an explicit when/when-not to use it.

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