List records

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

With no annotations provided, the description carries the full burden. It discloses the key behavioral trait of returning only a single page (up to 100 records), which is important for an agent to know. It does not mention output format or error behavior, but the single-page limitation is well conveyed.

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 well-structured sentence that front-loads the core purpose and immediately states the key constraint. No wasted words.

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 there is no output schema, the description adequately covers pagination and optional parameters. However, it does not explicitly describe the return value structure (e.g., array of record objects with fields), which would be valuable in the absence of an output schema.

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 schema already provides descriptions for all parameters (100% coverage), so the baseline is 3. The description adds value by summarizing how parameters work together (optional view, page size, max records, filterByFormula) and clarifying the single-page constraint that gives meaning to pageSize and maxRecords.

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 tool lists records from an Airtable table, with a specific verb 'list' and a resource. It distinguishes from siblings like get_record by noting it returns multiple records (up to 100) and includes optional view, page size, max records, and filterByFormula.

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 for reading multiple records with optional filtering and pagination, providing clear context. However, it does not explicitly mention when to choose this over search_records or get_record, such as 'for complex searches use search_records'.

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