Get record

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

The annotations declare readOnlyHint and idempotentHint, and the description ('Retrieve') is consistent with these. The description adds no additional behavioral context such as error handling, return format, or authorization requirements, but the annotations cover the safe read operation, so the description meets the baseline without contradiction.

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 concise sentence that gets directly to the point without unnecessary words. It is well-structured and front-loaded with the primary action, making it efficient and easy to parse.

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 simple read tool, the description provides the minimal necessary information, and the annotations and output schema fill some gaps. However, it lacks usage guidance, parameter explanations, and any mention of not-found behavior, making it only marginally complete for an agent needing broader context.

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 has no descriptions for any of the three required parameters (baseId, table, recordId), and the description does not explain their meaning or relationship. With 0% schema description coverage, the tool description fails to compensate, leaving the agent to rely solely on parameter names.

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 retrieves a single Airtable record, using a specific verb ('Retrieve') and resource ('Airtable record'), and the word 'one' distinguishes it from list_records. However, it does not explicitly contrast with sibling tools or explain the recordId parameter, so it is clear but not fully differentiating.

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 get_record versus list_records or other alternatives. The description gives no context or exclusions, leaving the agent to infer usage solely from the tool name and schema.

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