list_organization_connections

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

Annotations are absent, so the description carries the full burden. It only restates input requirements and the basic list action; it does not disclose whether the call is read-only, what the response contains, whether pagination applies, or any authentication constraints.

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 only two sentences and gets to the action immediately. The grammar is slightly rough ('connection' vs 'connections') and the environmentId requirement duplicates schema info, but no filler is present.

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 simple two-parameter list tool, the core call is described, but there is no output schema and the description does not mention return type, pagination, or how this differs from the sibling list_environment_connections. These are material gaps for an agent deciding both selection and result handling.

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?

With 0% schema description coverage, the description partially compensates by naming both parameters and giving example formats (env_<number>, org_123). It does not explain the semantic relationship between environmentId and organizationId or define 'connection', leaving some ambiguity.

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 an explicit verb ('List') and names the target resource ('connections') scoped to 'the selected organization', so an agent can infer the tool's purpose. It does not explicitly contrast itself with list_environment_connections, but the organization scope is stated directly.

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 states the context (selected organization) and required parameters, but it never mentions when to prefer this over siblings like list_environment_connections or list_connected_accounts. The conditions for use must be inferred from the resource name rather than stated.

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