post_webhook

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

Annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is covered externally. The description adds nothing of its own: it does not mention required auth, the required secret/events fields, side effects, or what the created webhook returns. With annotations present the bar is lower, but zero added context still merits a low score.

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 two sentences are redundant — the second merely repeats the first with 'new' inserted. Nothing is front-loaded because nothing of substance is present; the length is wasted rather than efficient.

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 mutation tool with a nested required body of five fields, no output schema, and no annotation-detail beyond hints, the description is completely inadequate. An agent cannot determine required inputs, side effects, or the resulting resource from this text.

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 description coverage is 0% at the top level, and the tool takes a single nested 'body' object requiring project_id, name, events, url, and secret. The description says nothing about any of these fields or their formats/constraints, leaving the agent with no added meaning whatsoever.

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 says 'Create a webhook. Create a new webhook.' — a plain restatement of the tool name with no scope, no resource qualifiers, and no distinction from siblings like put_webhook or delete_webhook. It is a tautology rather than an explanation of what the tool actually does.

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?

There is no guidance on when to use this versus put_webhook (update), post_webhook event collection, or any other sibling. No prerequisites, no conditions, no alternatives are named.

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