deleteForm

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

Beyond annotations (destructiveHint, idempotentHint), description adds that delete is permanent, cannot be undone via API, no soft-delete, and child fields become orphaned. This gives critical behavioral 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?

Description is concise with clear sections (use when, required, see also, destructive, returns). Each sentence adds value. Slightly verbose with return format example but overall well-structured.

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 simple delete tool with one parameter, description covers purpose, usage, behavior, return format, and warnings. No output schema needed because return is clearly described. Complete for agent use.

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 has one parameter with 0% coverage, but description explicitly states 'Required: form_id' and 'delete a form record by ID.' However, it does not add further constraints or format details beyond what the schema indicates.

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 'Delete a form - Permanently delete a form record by ID.' The verb 'delete' and resource 'form' are specific. It distinguishes from sibling tool `updateForm` which modifies without removing.

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 'Use when: removing a form - child fields orphan.' and 'See also: updateForm (modify without removing).' Also advises confirming intent with user before bulk use, covering when-not-to-use.

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