list_connections

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

With no annotations provided, the description carries the burden of behavioral disclosure. It says 'List all' but doesn't disclose that pagination via limit and cursor may be required to retrieve truly all connections. It also doesn't explicitly state that the operation is read-only, though that is implied. The phrase 'with their sync status' gives some return context but lacks details about pagination behavior.

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 two sentences, front-loaded with the core purpose, and contains no wasted words. It efficiently communicates the main function and optional filtering.

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?

Without an output schema, the description should clarify return values. It mentions 'sync status' but does not explain pagination details, default limits, or how to handle cursors. Given the pagination parameters, the description is somewhat incomplete for a list operation that may not return all results in a single response.

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% for all three parameters, so the baseline is 3. The description only repeats the group filter concept ('Optionally filter by group') and adds no additional meaning beyond what the schema already provides.

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 action ('List') and the resource ('Fivetran connections (connectors)') and distinguishes itself from siblings like get_connection_details (singular) and get_sync_status (specific status) by indicating it returns connections with sync status. The optional group filter aligns with the group_id parameter.

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 when to use the tool (when you need a list of connections) and mentions an optional filter. However, it does not explicitly state when to use alternatives, such as get_connection_details for a single connection or get_sync_status for a specific sync status, which is a missing exclusion.

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