Create a webhook.

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

Annotations already declare destructiveHint=true, idempotentHint=false, openWorldHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing on top — no note that this performs an external POST to the supplied URL, that it is non-idempotent (duplicate webhooks on retry), or that the 'confirm' flag is required for the mutation to take effect.

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?

Four words with no wasted clauses, but this is under-specification rather than genuine conciseness — there is no front-loaded substance to be concise about. The brevity comes at the cost of all useful content.

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 7-parameter mutation tool with a nested required-object payload, a confirm gate, and mutually exclusive body-passing mechanisms (payload vs. payload_file vs. body flags), plus no output schema, the description is wholly inadequate. Nothing an agent needs to invoke this correctly is present.

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 100%, so the schema already documents all seven parameters, giving a baseline of 3. The description adds no meaning beyond the schema — it does not clarify the confirm gate, the payload vs. payload_file mutual exclusion, or the required subfields (name, post_url, events) inside the nested payload.

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?

Tautological: description restates name/title.

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 when-to-use, when-not-to-use, prerequisites, or alternative routing is given. It does not mention list_webhooks, get_webhook, update_webhook, or delete_webhook, nor any condition that would select this tool over them. Zero guidance.

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