reach_deleteFormV1

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that deletion is permanent, cascades to the template, is blocked when submissions exist (to prevent silent data loss), and that views do not block deletion. This is rich, safety-relevant context beyond what any schema or annotation could infer.

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 compact and front-loaded with the primary action. Each sentence adds meaningful information: the action, the critical exception, and the view nuance. No filler or 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 destructive delete tool with only two simple parameters and no output schema, the description covers all essential behavioral aspects: permanence, template cascade, the submission guard, and the alternative to pausing. It is complete given the tool's simplicity.

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?

The input schema already provides 100% coverage with descriptions for both parameters (formUuid and profileUuid). The description does not add meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 opens with 'Permanently delete a form together with its template,' which clearly states the action (delete), the resource (form), and an important scope (also deletes the template). This distinguishes it from sibling tools that delete contacts, tags, segments, or other entities.

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?

It explicitly warns against deletion when a form has captured submissions and recommends pausing the form instead: 'pause the form instead to stop it collecting new ones.' It also clarifies that views alone do not prevent deletion. This gives clear when-to-use and when-not-to-use guidance, including an alternative action.

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