Webform Update

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

No annotations are provided, so the description carries the full behavioral burden. It discloses nothing about permissions required, whether updates are partial or full replacements, mutability/reversibility, or side effects on existing submission data—for a mutation tool this is a serious gap.

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 sentence is short but that brevity reflects under-specification rather than conciseness. There is no useful information to front-load, so the minimal structure earns no credit.

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 5-parameter mutation tool with no annotations and the only schema documentation being the parameter names themselves, the description is entirely inadequate. Although an output schema exists (removing the need to document return values), virtually everything else an agent needs is absent.

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?

All five parameters (label, status, elements, webform_id, description) have 0% schema description coverage and no meaning is added in the description. The agent cannot tell whether optional fields are merged or replace existing values, nor what shape 'elements' expects.

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 'Update a webform' merely restates the tool name and title 'Webform Update' with no added specificity. It does not indicate what aspect of a webform is updated (label, status, elements, description) nor differentiate it from sibling tools like webform_create, webform_get, or webform_delete.

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 guidance on when to use this tool versus alternatives. With siblings such as webform_create, webform_get, webform_delete, and webform_element_create present, the agent receives no signal about selection criteria or preconditions.

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