createAirtableRecord

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

With no annotations, the description must carry the transparency burden, but it only states 'creates' without disclosing side effects, auth requirements, idempotency, or response/error behavior. For a mutation tool, this is under-specified.

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, direct sentence with no redundant words or filler. It effectively states the purpose without extraneous detail.

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 no output schema and no annotations, the description offers no information on return values, error conditions, or how to source baseId/tableId (e.g., via listAirtableBases/listAirtableTables). This is incomplete for a tool with nested object parameters and no other contextual safety information.

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?

The input schema already provides descriptions for all three parameters (100% coverage), so the baseline is 3. The description's mention of 'specified fields' adds marginal clarification, but the schema's own description for 'fields' uses 'update' wording which could create confusion; the tool description does not resolve this.

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 uses a specific verb ('creates') and resource ('new record'), with 'specified fields in the given table' clearly indicating the action and scope. This cleanly distinguishes it from sibling tools like listAirtableRecords and updateAirtableRecord.

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?

No guidance is provided on when to use this tool versus alternatives such as updateAirtableRecord, nor any mention of prerequisites like how to obtain baseId or tableId. The usage context is only implicit in the verb 'creates'.

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