delete_webhook_subscription

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

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses that the operation is blocked in read-only mode, which is a valuable behavioral constraint. However, it does not state whether deletion is permanent, idempotent, or any side effects, which are important for a destructive operation.

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 concise, with two short sentences. The core action is front-loaded, and the read-only note is additional relevant information. No redundant or filler words.

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 a single parameter and an output schema provided, the description covers the core action, the parameter meaning, and a behavioral constraint. It does not describe error cases or confirm whether deletion is permanent, but given the simplicity and the output schema, it is reasonably complete. The lack of annotation coverage is partially mitigated by the read-only note.

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 only defines subscription_id as an integer with 0% schema description coverage. The description compensates by stating the action removes a subscription 'by its ID', clarifying that the integer parameter represents the identifier. This adds the necessary semantic meaning beyond the raw schema.

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) and the resource (webhook subscription) with the identifying parameter (by its ID). It distinguishes itself from sibling tools like list_webhook_subscriptions and create_webhook_subscription by its destructive verb, though it does not explicitly name them.

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 limited usage guidance. It implies this tool is for removing a specific webhook subscription, and the note 'Blocked in read-only mode' tells the agent when not to use it. However, it does not explain when to choose this over other operations or provide any conditions or prerequisites.

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