configure_webhook

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

With no annotations, the description fully discloses that the webhookSecret is shown only once and must be stored immediately, and that signatures use HMAC-SHA256. It doesn't mention if updating replaces the existing webhook, which is a minor gap.

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: two sentences plus an important warning in a separate sentence. No unnecessary words, and the critical information about the secret is highlighted.

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 tool with no output schema, the description covers purpose, events, secret handling, and protocol. It is self-contained and provides enough information for correct usage.

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?

Schema coverage is 100%, baseline 3. The description adds meaningful context: 'Your public HTTPS endpoint to receive POST webhook events. Must be reachable from the internet.' This clarifies the requirement beyond the schema's format.

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 'Register or update a webhook URL to receive real-time task event notifications' and lists specific event types, making the purpose unambiguous. It distinguishes from siblings by focusing on webhook configuration, while siblings are about tasks, approvals, etc.

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 implies when to use: to receive notifications for task events. It does not explicitly mention alternatives, but there are no sibling webhook tools. The warning about the secret being shown once adds important usage context.

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