delete_webhook_subscription

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

With no annotations, the description carries the burden of behavioral disclosure. It states the tool is destructive ('Remove') and adds a specific operational constraint: 'Blocked in read-only mode.' This is valuable context beyond the schema, but it does not disclose other important behaviors such as irreversibility, failure modes, or permission requirements. It provides some transparency but not comprehensive behavioral detail.

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 exceptionally concise, consisting of two short sentences. Each sentence provides distinct, useful information: the action and a critical operational constraint. There is no redundancy or filler, making it easy for an agent to parse quickly.

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 delete operation with a single parameter and an output schema, the description covers the essential purpose and a key constraint. The output schema presumably documents return values, so the description does not need to. It is adequate, though it could optionally mention that deletion is permanent, which would make it more complete. Overall, it is sufficiently complete for 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 schema has zero description coverage for the single parameter, so the description must compensate. It does so partially by saying 'by its ID' which clarifies that subscription_id is the identifier of the subscription to remove, matching the parameter name. However, it offers no additional meaning about the parameter's format, range, or where to find valid IDs, so the compensation is minimal.

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 ('Remove'), the resource ('webhook subscription'), and the scope ('by its ID'). It unambiguously distinguishes this tool from its siblings like 'create_webhook_subscription' and 'list_webhook_subscriptions', which perform different actions on the same resource.

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 usage is implied: an agent would use this to delete a webhook subscription when it has the ID. However, there is no explicit mention of when to use this versus alternatives, nor any guidance on prerequisites (e.g., how to obtain the ID, such as by using list_webhook_subscriptions). The read-only mode restriction provides a constraint but does not offer comparative usage guidance.

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