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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description contributes useful content detail (it surfaces sheets/tables/bases/CRM objects, so the agent knows the result shape is heterogeneous across destination types), but it says nothing about pagination despite a cursor parameter, nor about how much of an external account is traversed.

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?

One sentence, front-loaded with the verb and the returned resource types, with no filler. Its brevity is efficient rather than padded, though it leans toward under-specification given the undocumented parameters.

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 an open-world, paginated listing tool with three entirely undocumented parameters and no output schema, a single sentence is not enough. The agent cannot tell what base_id does, how to page with cursor, or what happens when the connection spans multiple destination types.

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 0% across three parameters, so the description carries the full burden and does not meet it. 'Connected account' loosely implies connection_id, but base_id (presumably scoping to one Airtable base) and cursor (presumably pagination) are never mentioned or explained anywhere.

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 ('Lists') and enumerates the resource types returned (sheets, tables, bases, CRM objects) scoped to 'a connected account'. This is far more informative than the title ('Pick where records go'), but it never distinguishes itself from nearby siblings such as list_connections, get_connection_columns, or list_destination_syncs.

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?

There is no when-to-use guidance at all: nothing says this should be called before save_connection_destination or send_to_destination, nor whether it is an alternative to list_connections. The only inferable context is that a connection must already exist, and even that is left to the agent.

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