list_destinations

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

No annotations provided, so the description carries full burden. It includes a prominent pagination warning ('RESULTS ARE PAGINATED'), which is a behavioral trait not obvious from the schema alone. It does not mention other traits like idempotency or authorization, but for a list operation this is acceptable.

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 sentence with a warning emoji, extremely concise and front-loaded. Every element adds value; there is no redundancy or fluff.

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?

While the description covers the core purpose and pagination, it omits return format details and prerequisites. The tool is relatively simple, so this is adequate but not fully complete for an agent to understand the full context without additional inference.

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 100%, so the schema already explains each parameter. The description does not add new parameter-level details but the pagination warning indirectly adds context to cursor/limit. The required 'schema_file' parameter has a detailed schema description, so overall parameter semantics are well-covered.

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 'Returns a list of all accessible destinations within your Fivetran account,' using a specific verb and resource. It distinguishes from siblings like 'destination_details' (which returns a single destination) and 'create_destination'.

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 use for listing all accessible destinations. While it does not explicitly mention alternatives or when-not-to-use, the context signals and sibling tools provide enough differentiation for an agent to infer when this tool is appropriate.

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