unregister_webhook

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

With no annotations, the description must disclose behavioral traits. It implies a removal/mutation operation but does not state whether the action is reversible, requires specific permissions, affects deliveries, or any other side effects. This falls short of full transparency.

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 concise sentence, but it is under-specified. It is not verbose, yet the brevity sacrifices necessary context, making it only minimally adequate.

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?

The tool has no schema details, no annotations, and no output schema, yet the description provides almost no context about behavior, return values, prerequisites, or effects. The Business plan note is the only extra context, which is insufficient for a webhook management operation.

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 parameters and the description does not explain how to identify the webhook to unregister. Given that the schema allows additional properties, the agent is left without any guidance on expected inputs, so the description fails to compensate for the empty 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 ('Unregister a webhook') with a specific verb and resource, and it is distinguishable from sibling webhook tools like list_webhooks and test_webhook. However, it lacks any additional detail about the exact scope or effect of unregistering, so it is not quite a 5.

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 such as list_webhooks or test_webhook. There is no mention of prerequisites, exclusions, or alternative tools, leaving the agent without context for appropriate invocation.

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