deleteFormField

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

Goes beyond destructiveHint annotation by explaining permanence, unrecoverability, orphan metadata, and return format. No contradictions with annotations.

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?

Concise, well-structured with sections. Every sentence adds value: purpose, usage, requirement, caution, alternative, return message.

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?

Comprehensive for a simple destructive tool; covers deletion impact, confirmation guidance, and return format despite no output schema.

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?

With 0% schema coverage, description states required field_id and its role in context. Parameter name is self-explanatory; could explicitly state it's the ID of the form field.

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?

Clearly states the tool deletes a form field permanently. The description distinguishes it from sibling tools like updateFormField by emphasizing destructive nature.

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' condition, warns of orphan metadata, includes 'See also' for alternative, and advises user confirmation for bulk operations.

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