delete_fields

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

Adds significant context beyond annotations: safety guard with expectedName, sequential processing, partial results on failure, checkpoint for resumability, and force parameter for dependencies. No contradiction 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?

Single, focused paragraph that front-loads the main action and essential behaviors. Every sentence adds information with no 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?

Covers key behaviors (safety, partial results, checkpoint, force) for a destructive batch operation. However, the return value format is not described; it only mentions 'partial results are always returned' without detail.

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 coverage is 100%, but description adds meaning: the expectedName is a safety guard, checkpoint enables resumption, force handles dependencies, and debug adds diagnostics. Adds value beyond schema descriptions.

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 it deletes multiple fields from an Airtable table. Differentiated from sibling tools like 'delete_field' (singular) and 'update_field_config' (modification, not deletion).

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 context for batch deletion with safety guard, sequential processing, and optional checkpoint. However, it doesn't explicitly say when to prefer this over the singular 'delete_field' tool.

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