delete_form

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

Annotations already convey destructive intent, but the description adds substantial behavioral context: the soft-delete behavior, hiding from list_forms, 5-day retention and auto-purge, reversibility via restore_form, owner/team-owner authorization, and preservation of submission records. This goes well beyond the structured annotation data.

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 dense, purposeful sentences, each contributing essential information: the action and scope, lifecycle and recovery behavior, and permission requirements plus submission handling. No filler or redundant repetition of schema content.

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?

The description is complete for this tool's complexity: it covers scope, effects, recovery, retention, permissions, and data preservation. With an output schema present, return values need not be described, and the annotation set already covers read/destructiveness.

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%, and the single parameter formId is fully described in the schema itself. The description doesn't add extra parameter-level detail, but none is needed given the simple one-parameter interface.

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: 'Move a form into the trash (soft delete)'. It clearly distinguishes itself from siblings by explicitly contrasting with list_forms and restore_form, and by describing the soft-delete semantics.

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?

Provides explicit context for when to use the tool: when you want to soft-delete a form. It names restore_form as the way to undo, specifies the 5-day recoverable window, and gives an explicit permission constraint ('Only the form owner / team owner can delete'), which acts as a when-not condition.

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