list_connections

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

There are no annotations provided, so the description must carry the full burden of disclosing behavior. The description just says 'List' without revealing that the operation is read-only, that it returns a paginated result, or that it does not modify state. It adds no information beyond the obvious list intent.

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, short sentence which is concise, but it omits essential details about pagination and parameters. It is not structured to front-load the most useful constraints or intent behind the list operation. The brevity is a trade-off with completeness.

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?

This is a list tool with two parameters and no output schema or annotations. The description provides only a minimal statement, leaving the agent with no understanding of what a 'connection' consists of, how pagination works, or what the return structure is. This is heavily insufficient for correct usage.

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%, and the description does not explain the two parameters 'page' and 'per_page' at all. An agent has no idea that 'per_page' controls page size or that 'page' starts at 1. The description fails to compensate for the lack of schema details.

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 states a clear action ('list') and a clear resource ('connections'), and the 'configured in the account' clarifies scope. It is distinct from get_connection (which likely retrieves a single connection) and from list_custom_connectors (which lists a different resource). However, it does not elaborate on what counts as a connection or which account is meant.

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 provides no guidance on when to use this tool versus list_custom_connectors or get_connection. It does not mention any typical scenarios, exclusions, or criteria that would help an agent decide between the siblings.

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