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

Annotations already flag destructive=true, non-idempotent and open-world, so the safety profile is covered. The description adds materially beyond that: the auth/scope requirement and the crucial caveat that a boolean response means 'request accepted', not 'actually pushed' — a behavior an agent would otherwise misread as success. It doesn't explain why it's destructive (e.g. row creation vs overwrite) or what happens on repeated pushes despite idempotent=false.

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?

Three tight sentences: action first, prerequisites second, return-shape caveat last. Every sentence carries distinct information and nothing is padded.

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?

With no output schema, the description does the important work of explaining what the return value does and does not mean. For a destructive, non-idempotent write tool it could still say more about duplicate pushes or failure modes, but an agent has enough to call it correctly and interpret the result.

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 coverage is 100%, so baseId, tableIds, callUUID, account and workspace are all documented in the schema itself. The description only restates the cardinality constraint ('one base + one or more tables'), adding marginal value. Baseline 3 is appropriate.

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 ('Push') plus the exact resource and shape ('a call's extracted tasks into Airtable rows under one base + one or more tables'). The Airtable target distinguishes it cleanly from hub_send_call_to_jira and hub_send_call_to_clickup without needing to open either 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?

Gives concrete prerequisites (recordings:write scope AND a workspace Airtable integration), which is real selection guidance for a connector tool. It stops short of an explicit 'use this when the user wants Airtable rather than Jira/ClickUp' statement, so there's a small gap versus a 5.

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