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

Annotations already declare readOnlyHint=true and openWorldHint=true, but the description adds real substance beyond that: the OAuth scope is airtable.readonly, only SELECT queries succeed, and DDL/DML/scripts are rejected by Google. That tells the agent exactly what will fail and why, which is the failure-mode context annotations alone do not provide.

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?

Front-loaded with the purpose and workflow position, then numbered prerequisite steps. Every sentence carries information; the only minor redundancy is restating 'IMPORTANT: Always call step 2' when step 2 was already described above.

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?

Has an output schema, so return values need no explanation, and the description covers workflow prerequisites, the read-only constraint, and failure modes. The remaining gap — the body payload format — is handled by an explicit instruction to retrieve it externally, which is adequate though not self-contained.

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?

There is one parameter (body) as a free-form object with additionalProperties=true and 0% schema description coverage, so the schema explains nothing. The description cleverly compensates by directing the agent to fetch the exact body structure via query_contexts action_details, but it never describes the body's shape or required fields itself, leaving the agent dependent on a prior call.

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?

States a specific verb and resource ('Query Airtable data') and anchors it as step 3 (FINAL) of a workflow, which tells the agent where it sits relative to query_contexts (steps 1-2). It never names execute_action, so the read/write split between siblings is only implied via the read-only note rather than stated.

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?

Gives explicit, ordered prerequisites (request='accounts' then request='actions_details') with the exact request values and a hard instruction: 'Always call step 2 to see the exact body structure before querying.' When-to-use, ordering, and the required prior tool are all spelled out.

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