list_cloud_flow_connections

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

Beyond readOnlyHint=true, the description discloses two substantive behavioral traits: connection IDs are withheld from results, and the listing is not validated for validity, permissions or licensing. Those are real caveats an agent needs when deciding whether the output is trustworthy. It does not mention pagination or result shape, which keeps it from a 5.

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 tight sentences with no filler, and the core scoping statement ('list visible connection reference metadata') is front-loaded ahead of the caveat. The second sentence is clipped to the point of near-fragment status, which is efficient but slightly at odds with readability.

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 read-only listing with no output schema and only two optional parameters, the description covers what is returned and its limits, which is the essential part. However, it says nothing about result size, ordering, how 'top' affects output, or what a 'visible' connection actually means in scope terms.

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 50%: environment_profile is documented in the schema, but 'top' (an integer with a 1-100 range) has no description anywhere. The description mentions no parameters at all, so it fails to compensate for the uncovered half, and adds no meaning such as ordering or default page size.

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?

States a specific verb and resource: 'List visible connection reference metadata'. The subject matter (connection references) naturally separates it from siblings like list_cloud_flows and list_cloud_flow_runs, and the 'without exposing connection IDs' clause further narrows what comes back. It stops short of naming a sibling explicitly, so it is clear but not maximally differentiated.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative. The caveat that validity, permissions and licensing are 'not established' hints at cases this tool cannot serve, but the agent is left to infer that it should look elsewhere for verified or permission-relevant information.

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