Webform Delete

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure, yet it only implies destruction through the verb "delete." It says nothing about irreversibility, whether associated submissions are cascade-deleted, required permissions, or any confirmation/rollback behavior.

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 single sentence is front-loaded with no wasted words, but it is under-specified rather than concise. It reads as an expedient label more than a structured description.

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 explained, but for a destructive operation with no annotations and zero parameter coverage, the description is far too thin. Critical context about data loss and identifier sourcing 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?

Schema description coverage is 0% and the single parameter webform_id is undocumented in both schema and description. The description does not compensate by explaining the identifier's format, source, or how to obtain it (e.g., from webform_list).

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?

"Delete a webform" gives a specific verb and resource, so the basic operation is unambiguous. However, it offers no differentiation from sibling webform tools (webform_list, webform_get, webform_create, webform_update) or from the adjacent webform_submission_delete, leaving the agent to infer scope from the name alone.

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 statement of when to use this tool, what prerequisites exist, or which sibling to prefer for related tasks. The agent receives no guidance beyond the bare verb, which is the minimum before guidance is considered present.

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