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

Annotations already declare destructiveHint=true and idempotentHint=true, so the agent knows this is a permanent mutation. The word 'Permanently' reinforces irreversibility, which is genuinely useful given sibling restore tools exist elsewhere, but the description adds nothing about permissions, cascade effects, or error behavior. Adds some value over annotations, not rich context.

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?

A single six-word sentence with the destructive verb front-loaded: efficient, but the brevity is under-specification rather than deliberate compression. Nothing is wasted, yet almost nothing is delivered.

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 an irreversible mutation with two undocumented required parameters and no output schema, the description should at minimum identify the identifiers and confirm what happens to related data. Annotations cover the safety profile, but the calling contract remains underspecified.

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 description never mentions websiteId or submissionId, so no meaning is added beyond the bare property names. The names are largely self-explanatory, which keeps this above a 1, but the description fails to compensate for the coverage gap.

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 (deletes) and a bounded resource (one submission), and 'one' clarifies it is single-item rather than bulk. It does not explicitly distinguish itself from nearby siblings like websiteForms_submissions_setStatus or websiteForms_submissions_list, but the mutate-and-remove intent is unambiguous.

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?

No guidance on when to call this versus alternatives such as websiteForms_submissions_setStatus (soft status change) or the cms_items_restore pattern. Prerequisites and the fact that this is not recoverable via a restore sibling are left entirely to inference.

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