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

Annotations already mark the tool as non-read-only and non-idempotent, consistent with the 'Create' action. The description adds useful context about the behavior (inbound receives POSTs, outbound sends events to URL) but does not mention prerequisites, return values, or error handling. It adds some value beyond annotations without being comprehensive.

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 exactly two sentences, front-loaded with the primary purpose, and contains no filler or redundant information. Every clause earns its place.

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 tool's moderate complexity (6 params, 1 enum, no output schema), the description adequately covers high-level behavior and direction, plus compatibility context. It falls short of explaining return values or exact prerequisites, but the schema and annotations compensate for most structured information, making this reasonably complete.

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 covers 100% of parameters with descriptions, so the description adds little beyond the schema. It does clarify the `type` parameter's direction and mentions compatible platforms for outbound webhooks, but does not provide additional syntax or usage details. Baseline of 3 is appropriate for high schema coverage.

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 'Create an inbound or outbound webhook for an agent' with specific verb (create) and resource (webhook). It distinguishes between inbound and outbound use cases, and the webhook-specific purpose is clear from the sibling context of other integration tools (email, slack, telegram, 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 explains when each direction is appropriate ('Inbound: receive messages via HTTP POST', 'Outbound: send events to your URL'), and mentions popular integration platforms (n8n, Zapier, Make) as context. However, it does not explicitly list alternatives or when not to use this tool, leaving the guidance slightly implicit.

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