webhook_create

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

Annotations are all false, so the description carries the burden. It mentions creation (not read-only) and error behavior (422), but does not disclose idempotency, duplicate handling, or safety beyond that. Some behavioral context is added, but not 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 two sentences plus a concise matrix, all front-loaded and free of redundancy. Every sentence provides essential information, making it efficient and easy to scan.

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 no output schema, the description does not explain what the tool returns (e.g., created webhook ID). It covers parameter semantics well but lacks return value information. With 8 parameters and minimal annotations, it leaves some gaps in completeness.

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 88% with descriptions. The description adds value by clarifying required vs optional, defaults (enabled=true, source='api'), and the target-event matrix. However, it omits the 'site' parameter (required) from the description text, relying solely on the 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 'Create a webhook (POST /webhooks)', identifies the HTTP method and endpoint, and specifies that the body is flat (no envelope). This distinguishes it from sibling tools like webhook_delete, webhooks_list, and webhook_update.

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 lists required and optional parameters with defaults (enabled, source), and provides a detailed matrix of valid target+event combinations. It also notes that Voog returns 422 for invalid combinations, guiding proper use. However, it does not explicitly state when to use this tool over alternatives.

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