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

Annotations already declare readOnlyHint=true, so the safe-read nature is covered. The description adds useful domain context (webhooks push submissions to external URLs, payload settings included), but says nothing about return structure, ordering, or permissions for the endpoint.

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?

Two tight sentences with the core purpose front-loaded and the endpoint hint appended; nothing is wasted.

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 single-parameter read-only list operation with annotations covering the safety profile and full schema documentation of the parameter, the description is largely sufficient. It could mention pagination or the shape of returned webhook data, but no output schema exists to leverage either.

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 (form_id), documented at 100% coverage by the schema itself. The description's phrase 'a form's webhooks' reinforces the scoping but adds no syntax or format detail beyond the schema, so the 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 (list) and resource (webhooks) scoped to a form, and clarifies what webhooks are (pushing submissions to external URLs with payload settings). This distinguishes it cleanly from the sibling formstack_create_webhook.

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 implies reading existing webhook configuration for a form, but gives no explicit when-to-use guidance, prerequisites, or reference to alternatives like formstack_create_webhook for creating them. Usage is inferable but not stated.

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