wp_list_form_webhooks

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. 'List' reasonably signals a read-only operation and the Ninja Forms prerequisite is disclosed, but the description does not cover failure behavior (e.g., what happens when Ninja Forms is absent or the form_id does not exist) or the return format.

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 description is a single front-loaded sentence with no filler; the verb and resource lead. The only minor flaw is the redundancy of 'Ninja Forms' appearing twice, once in the resource phrase and once as the prerequisite parenthetical.

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 simple one-parameter list tool with 100% schema coverage, the description is nearly sufficient: the agent knows what to call and which ID to pass. However, with no output schema and no annotations, the description does not clarify what a returned 'webhook action' looks like or how prerequisite failures surface, leaving mild ambiguity about the result.

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% — the single required parameter form_id is already documented as 'Ninja Form ID' in the schema. The description adds no parameter-level detail, so the baseline of 3 applies; nothing more is needed.

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 uses a specific verb ('List') and a specific resource ('Ninja Forms webhook actions on a form'), and the 'Ninja Forms' + 'on a form' qualifiers differentiate it from siblings like wp_list_custom_webhooks and wp_list_woocommerce_webhooks. The term 'webhook actions' is slightly ambiguous — it is not clear whether it lists configured webhook endpoints or available action topics — which keeps it from a 5.

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 provides no when-to-use or when-not-to-use guidance and names no alternatives. The parenthetical '(requires Ninja Forms)' hints at a prerequisite but does not help an agent choose between this tool and the many webhook-related siblings such as wp_list_custom_webhooks, wp_list_webhook_topics, or wp_list_woocommerce_webhooks.

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