pylon_delete_webhook

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a deletion operation, implying it's destructive, but doesn't specify whether deletion is permanent, requires specific permissions, or has side effects like stopping notifications immediately. For a mutation tool with zero annotation coverage, this leaves significant gaps in understanding the tool's behavior.

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 zero waste: the first states the purpose, and the second provides usage context. It's front-loaded with the core action and efficiently conveys necessary information without redundancy or unnecessary elaboration.

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?

Given the tool's complexity (a destructive operation with no annotations and no output schema), the description is adequate but incomplete. It covers the purpose and usage context but lacks details on behavioral aspects like permanence, permissions, or response format. For a deletion tool, more transparency would be beneficial to ensure safe and correct usage.

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 input schema already fully documents the single parameter (webhook_id). The description adds minimal value beyond the schema by implying the parameter is used to identify the webhook to delete, but doesn't provide additional syntax, format, or usage details. This meets the baseline of 3 when schema coverage is high.

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 specific action ('Delete an existing webhook') and resource ('webhook'), distinguishing it from sibling tools like pylon_create_webhook or pylon_get_webhooks. It uses precise language that directly conveys the tool's function without ambiguity.

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 explicit context for when to use this tool ('when removing integrations or cleaning up unused webhooks'), which helps the agent understand appropriate scenarios. However, it doesn't explicitly mention when NOT to use it or name alternatives, such as using pylon_get_webhooks first to identify webhook IDs, which would elevate it to a 5.

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