Delete form

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

Annotations already mark the tool as destructive and non-read-only, but the description adds genuinely useful behavioral context: deletion is permanent, the template is removed too, submission-bearing forms are protected, and views do not prevent deletion. This goes well beyond what the annotations communicate.

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 tight and well-structured: the primary action comes first, followed by the critical deletion constraint, the recommended alternative, and an important edge-case clarification. Every sentence earns its place with no redundancy.

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 two-parameter destructive delete with no output schema, the description is complete. It explains the permanent scope, the precondition for deletion, the alternative action, and the fact that views do not block deletion, giving an agent everything needed to decide whether and how to call the tool.

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%, so the baseline is 3 even though the description itself adds no parameter-level meaning. The descriptions 'Form uuid parameter' and 'Profile uuid parameter' are minimal but present, and the tool description does not need to compensate.

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 clearly states the operation: 'Permanently delete a form together with its template.' It specifies both the resource and the destructive action, and is easily distinguishable from sibling read-only form tools like reach_getFormDetailsV1 and reach_listFormsV1.

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 explicitly warns when deletion is not allowed ('a form that has already captured submissions cannot be deleted') and provides the recommended alternative ('pause the form instead'). It also clarifies that views alone do not block deletion, giving the agent concrete decision guidance.

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