create

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the 'dryRun' requirement, which is a behavioral constraint, but doesn't cover other important aspects like permissions needed, rate limits, error handling, or what happens on successful creation. It adds some context but leaves significant gaps for a mutation tool.

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 purpose and immediately follows with the critical usage requirement. There's zero waste—every word earns its place by providing essential information without redundancy or fluff.

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 that there's an output schema (which handles return values), the description doesn't need to explain outputs. However, for a mutation tool with 6 parameters, 0% schema coverage, and no annotations, the description is incomplete. It covers the dry-run requirement well but misses other contextual details like error conditions or side effects, making it only partially adequate.

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 0%, meaning none of the 6 parameters have descriptions in the schema. The description only mentions 'dryRun' implicitly and doesn't explain any other parameters like 'baseId', 'table', 'records', 'typecast', or 'idempotencyKey'. It fails to compensate for the lack of schema documentation, leaving most parameters semantically unclear.

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 action ('Create Airtable records') and specifies the resource ('Airtable records'), which is a specific verb+resource combination. However, it doesn't explicitly distinguish this tool from its sibling 'upsert' or 'update' tools, which likely handle similar record operations. The purpose is clear but lacks sibling differentiation.

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 provides explicit usage guidance by stating 'requires diff-before-write via dryRun first,' which indicates a prerequisite workflow. This tells the agent when to use this tool (only after a dry run) and implies an alternative approach (using dryRun parameter). It gives clear context for proper invocation.

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