Delete Webhook

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

The description accurately notes the destructive nature of the tool, which aligns with the openWorldHint annotation. However, it adds no additional behavioral detail beyond what is obvious from the name and schema.

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 sentence that conveys the essential information without any fluff. Every word earns its place.

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 deletion tool with one parameter and no output schema, the description is sufficient. It could optionally mention that the webhook is permanently removed, but the tool is effectively 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?

With 100% schema description coverage, the description 'Delete an inbound webhook from a bot' does not add new meaning to the parameter 'id', which is already described as 'The ID of the webhook to delete'. The baseline score of 3 applies.

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 action ('Delete') and the target resource ('inbound webhook from a bot'), effectively distinguishing it from sibling tools like neuron_delete_outbound_webhook and neuron_create_webhook.

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, nor are there any prerequisites or context for invocation. The description assumes the agent knows to use this for inbound webhooks only.

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