Delete a form (irreversible)

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

With no annotations, the description carries the full behavioral burden and does well: it discloses irreversibility, that the public URL stops working immediately, and the tenant scoping of the target. It stops short of stating required permissions or error behavior for a missing/already-deleted id, which would be the remaining disclosure 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?

Three short sentences, front-loaded with the destructive nature and impact, then the prerequisite, then the safety constraint. No filler.

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 one-param destructive tool with no annotations and no output schema, the description covers impact, target scope, prerequisite lookup, and human-confirmation policy. Minor omissions like permission requirements or post-delete error semantics keep it from being fully complete.

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?

Only one parameter and schema coverage is 100%, so the schema already documents formId as the UUID to delete. The description adds tenant-scoping context but no format or sourcing detail beyond what the schema and the list_forms pointer provide; baseline 3 applies.

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 and resource ('Permanently delete a form') plus the scope ('belonging to the API key's tenant'). It is unmistakable against siblings list_forms, get_form, and create_form, which are all non-destructive or additive.

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?

Explicitly routes the agent to list_forms to obtain the id, and adds a hard when-not rule: confirm with the user, do not delete on your own initiative. Both the prerequisite and the prohibition are stated outright.

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