airtable-user-mcp

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

Annotations already indicate this is a non-read-only, non-destructive, non-idempotent operation. The description adds valuable context by specifying that cell value duplication is optional (defaulting to false), which helps the agent understand behavioral nuances beyond the annotations. However, it does not mention potential side effects like field ID changes or permissions required.

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?

The description is a single, efficient sentence that front-loads the core action ('duplicate/clone a field in a table') and includes the optional behavior without unnecessary details. Every word serves a purpose, making it highly concise and 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?

Given the tool's moderate complexity (mutation with optional behavior), no output schema, and rich annotations, the description is adequate but lacks details on return values or error conditions. It covers the basic operation but does not fully address what happens after duplication (e.g., new field ID, confirmation message).

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%, so the schema fully documents all 5 parameters. The description adds minimal value beyond the schema by implying the relationship between sourceFieldId and duplication, but does not provide additional syntax or format details. This meets the baseline for high schema coverage.

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 the specific action ('duplicate/clone a field in a table') and resource ('field'), distinguishing it from sibling tools like create_field, rename_field, or delete_field. It explicitly mentions the optional behavior of duplicating cell values, which further clarifies its unique function.

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?

The description implies usage when cloning a field, but does not explicitly state when to use this tool versus alternatives like create_field (for new fields) or update_field_config (for modifying existing fields). No exclusions or prerequisites are mentioned, leaving the agent to infer context from sibling tool names.

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