airtable_create_base_schema

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, and it delivers comprehensively with an 'Operational Disclosures' section. It discloses that tables are permanent, that creation is irreversible via this tool, that tables are created sequentially with 250ms spacing to avoid 429 rate limits, and that it requires a Personal Access Token with 'schema.bases:write' scope. This is exactly the kind of side-effect and prerequisite context an agent needs for a mutating provisioning 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 fully front-loaded with the core purpose in the opening sentence, then organized into scannable markdown sections. Every sentence earns its place: When to Use, When NOT to Use, and Operational Disclosures all carry distinct, non-redundant information. There is no filler or repetition.

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 complexity (multi-table provisioning with side effects) and the complete absence of annotations, the description covers purpose, usage boundaries, side effects, persistence, rate limits, and auth scopes thoroughly. The only gap is that no output schema exists and the description does not mention what the tool returns on success. For a provisioning tool the side-effect disclosure matters more than the return format, but a brief note on the response would make it fully complete.

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 baseline is 3. The schema already documents both base_id and the tables array structure with field types and options. The description adds minimal parameter meaning beyond the schema — it lists a few supported field types ('singleLineText, singleSelect, currency, number...'), which overlaps with the schema's own type list. The schema does the heavy lifting, so the description adds marginal but not essential value.

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 first sentence states a specific verb and resource: 'Provisions multiple tables and custom fields in an Airtable base using the official Metadata API.' It clearly distinguishes from siblings by naming airtable_modify_schema, airtable_batch_upsert, and airtable_list_schema as things it is not. An agent can tell exactly what this tool does versus its alternatives without opening any schema.

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 has explicit 'When to Use' and 'When NOT to Use' sections that name the alternative tools and the exact conditions that select them (single field → airtable_modify_schema, record insertion → airtable_batch_upsert, field ID inspection → airtable_list_schema). This leaves nothing to inference and directly routes the agent to the correct sibling.

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