Delete Webhook Subscription

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

The description goes beyond the destructiveHint annotation by specifying that 'Deliveries stop immediately' and 'the secretKey is not recoverable afterwards.' This discloses critical irreversible consequences and timing of the delete operation. It also aligns with the idempotentHint annotation (deleting an already-deleted subscription could be considered idempotent). No contradiction with annotations.

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 short sentences, with the action verb in the first word. It contains no filler or redundant statements. Every sentence adds essential information, making it exceptionally concise while still covering key behavioral details.

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 single-parameter delete tool with annotations for destructive/idempotent behavior, the description fully covers what happens (delete), how (by externalId), and consequences (immediate stop, secretKey loss). No output schema exists, so return values are not needed. The description is sufficiently complete given the tool's simplicity.

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 provides 100% coverage with a clear description for externalId ('Subscription externalId (from hyros_get_webhook_subscriptions)'). The description repeats 'by its externalId' but adds no new syntax or format details beyond the schema. Therefore, the baseline score of 3 applies, as the schema carries the semantic load.

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 begins with 'Delete a webhook subscription by its externalId,' clearly stating the action (delete), resource (webhook subscription), and method (by externalId). This distinguishes it from sibling tools like hyros_create_webhook_subscription and hyros_get_webhook_subscriptions. The additional consequence 'Deliveries stop immediately' reinforces the 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 clearly implies when to use the tool: when you need to permanently stop webhook deliveries. It states the deletion is by externalId, and the schema description points to hyros_get_webhook_subscriptions for obtaining that ID. However, it does not explicitly mention alternatives or exclusions, so it lacks the explicit 'when-not' guidance that would earn a 5.

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