Webform Handler List

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

With no annotations, the description carries the full behavioral burden. It does disclose a genuinely useful architectural fact (handlers are plugins read off the webform, not listable JSON:API entities), which explains why this tool exists. However it says nothing about permissions, pagination behavior, or the effect of a null webform_id, despite page_limit implying a paged result.

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?

Front-loaded with the core action in the first sentence, followed by a rationale sentence that earns its place by explaining the non-entity nature of handlers. No filler or repetition.

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?

An output schema exists, so return values need not be described, and a read-only listing is low-risk. Still, the two parameters are undocumented, and the ambiguity around an omitted webform_id and pagination leaves an agent guessing at call semantics.

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 0% for both parameters. The phrase 'attached to a webform' loosely implies webform_id, but page_limit is never mentioned and the nullable/default-null webform_id semantics (does it list handlers across all webforms?) are undefined. With low coverage the description needed to compensate and does not.

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 handlers attached to a webform.' It also explains what handlers are (plugins configured on the webform, not entities), which distinguishes this from a generic JSON:API resource list and from webform_list. It never names the closest siblings (webform_element_list, webform_handler_create), so it falls short of 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?

There is no explicit when-to-use or when-not-to-use guidance, and no pointer to webform_handler_create/update/delete for the modification path. Usage is only inferable from the verb 'List'. The prerequisite question — what happens when webform_id is omitted — is left entirely unanswered.

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