list_environment_connections

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

No annotations are provided, so the description carries the behavioral burden. 'List all connection' signals a read-only, unfiltered operation, but the description does not disclose return shape, pagination, error behavior, or any side-effect/authorization context.

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?

Two short sentences with no filler; the primary action is front-loaded and the parameter requirement follows immediately. Every sentence contributes useful information.

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 a one-parameter read-only list operation, the description supplies the essential purpose and the required argument format. It is slightly incomplete in not describing the returned connection objects, and it does not route around sibling tools, but these are minor gaps for a simple list call.

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 0%, but the description compensates by naming the required parameter and specifying the expected format 'env_<number>'. This adds meaning beyond the raw regex, though the pattern allows word characters beyond digits, so the format hint is slightly narrower than the schema.

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 uses a specific verb and resource ('List all connection... environment') and states the scope ('specified environment'). It is clear enough, but it does not explicitly distinguish this from the closely named sibling list_organization_connections, and the singular 'connection' is a minor ambiguity.

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?

It implies usage by saying it lists connections for an environment and adds an invocation prerequisite ('Requires environmentId parameter (format: env_<number>)'). However, it gives no guidance about when to prefer this over alternatives such as list_organization_connections or list_connected_accounts.

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