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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), yet the description still adds real value: URLs come back masked, there is a hard cap of 5 per site, and entitlement depends on plan tier. These are operational constraints an agent cannot get from the annotations. It stops short of describing ordering or empty-state behavior.

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?

One dense sentence that front-loads the verb and resource, then enumerates the payload contents. Every clause carries information, though the parenthetical definition and the return-field list make it slightly heavy for a single sentence.

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?

With no output schema, the description carries the return-value burden and does so by naming the masked URL, target forms (with the 'empty means all' semantics), latest delivery results, limit, and entitlement. That covers what an agent needs to interpret the response for this read-only, single-parameter tool.

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?

Only one parameter, fully documented in the schema (100% coverage) with guidance to draw the ID from list_sites. The description mentions 'the site's' but adds nothing about the ID format or validation beyond what the schema provides, so baseline 3 applies.

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?

States a specific verb+resource — 'List the site's form Webhooks' — and immediately defines the resource as 'endpoints that get a signed JSON POST for every inquiry', so an agent knows exactly what object class is being returned. The list verb naturally separates it from webhooks_get, webhooks_test, and webhooks_update, though no sibling is named explicitly.

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?

Usage is implied rather than stated: an agent can infer this is the way to inspect existing webhook configuration. There is no explicit 'use this when...' guidance, no mention of what to do if no webhook exists, and no pointer to webhooks_update for creating/changing one.

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