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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description restates "Read-only" (redundant) but does add genuinely new context: the webhook fires on the form.complete event for a template, and the underlying endpoint. It says nothing about pagination limits or what a webhook record contains, so it adds moderate rather than rich context.

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?

Three short sentences: the resource and event first, then the mutation profile, then the endpoint. Every sentence carries information and nothing is padded.

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 and full schema coverage on the three pagination/filter parameters, the description covers what an agent needs to call it correctly for a read-only list. The one soft spot is slight ambiguity about whether the tool returns only form.complete webhooks or all webhooks, which it never resolves.

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 page/page_size/template_id are already fully documented, and the baseline is 3. The description still adds meaning by explaining that a webhook is tied to a template (clarifying what template_id filters on) and by implying the list is scoped to form.complete events.

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 and resource ("List the webhooks") plus the triggering event (form.complete on template completion), which no sibling tool covers. The GET /v2/webhooks reference pins the exact operation, so an agent can distinguish it from the list_* form/template/user tools without opening the schema.

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: an agent should call this when it needs to inspect webhook registrations, and the event description scopes what those webhooks are. However, there is no explicit when-to-use/when-not-to-use statement and no alternative named, so the routing guidance is left to inference.

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