set_webhook

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

With no annotations, the description must disclose behavioral traits, but it only states the action without any details on side effects, permissions, idempotency, URL validation, or what happens to the existing webhook. This is a significant transparency gap for a mutation tool.

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 short sentence, but it is under-specified rather than appropriately concise. It omits essential context that would justify its brevity, making it feel incomplete rather than well-structured.

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 simple schema and no annotations, the description should still clarify the webhook URL's purpose, required setup, and potential implications. It does none of this, leaving the agent without enough context to safely invoke the tool.

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 has one parameter 'webhookUrl' with zero description coverage. The description merely echoes the parameter name, adding no semantic value about expected format, constraints, or examples. The description does not compensate for the schema's lack of detail.

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 'Set webhook URL' clearly states the action (set) and the resource (webhook URL), distinguishing it from the sibling 'get_webhook'. It is specific enough to understand the tool's core function, though it lacks additional context about the webhook's role.

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 'get_webhook' for retrieving the current webhook or other configuration tools. There are no prerequisites, examples, or exclusion criteria.

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