airtable-user-mcp

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

Annotations already indicate this is a mutation tool (readOnlyHint=false) that is non-destructive and non-idempotent. The description adds value by specifying what gets duplicated (configuration details), but doesn't disclose behavioral traits like permissions needed, rate limits, or what happens if the source view doesn't exist. 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 sentence, front-loaded with core action, zero waste. Every word earns its place by clarifying scope ('all its configuration') and examples ('filters, sorts, field visibility, etc').

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 mutation tool with no output schema and rich annotations, the description is adequate but has gaps. It explains what the tool does but lacks details on return values, error conditions, or dependencies. Given the complexity (duplicating configurations), more behavioral context would help.

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 no parameter-specific information beyond implying 'sourceViewId' is the view to duplicate and 'newName' is for the copy. Baseline 3 is appropriate when schema does the heavy lifting.

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 verb ('duplicate') and resource ('an existing view') with specific scope ('with all its configuration'), distinguishing it from sibling tools like 'create_view' (new view) or 'rename_view' (modify existing). It precisely defines what gets duplicated: filters, sorts, field visibility, etc.

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 needing a copy of an existing view with its configuration, but provides no explicit guidance on when to use this vs. alternatives like 'create_view' for a blank view or 'rename_view' for modifying an existing one. It mentions no prerequisites or exclusions.

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