list_connections

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

No annotations are supplied, so the description carries the full burden. "Metadata only" is a useful hint that secrets/credentials are excluded, but there is no disclosure of permissions required, pagination or ordering behavior, or whether results are cached/sensitive.

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 sentence is short and front-loaded with the verb, which is good, but at seven words it is terse to the point of under-specification rather than effectively concise. A single additional clause naming the returned fields would have been cheap and high-value.

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?

With no output schema and no annotations, the description is the only source of information about this tool, and it does not say what fields the connection metadata contains or how it is scoped. For a listing tool whose return shape is undocumented elsewhere, this leaves a substantive gap.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The single caveat is that the description cannot add meaning to an empty schema, and it does not clarify whether any implicit scoping (tenant, target) applies.

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 gives a verb ("List") and a resource ("connection metadata"), so the basic intent is legible, and "metadata only" hints at scope. However it does not differentiate from siblings such as get_connection_status or vault_list, leaving the agent to infer whether this returns connections, connection states, or something else.

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 statement of when to call this versus get_connection_status or vault_list. The word "only" implies a boundary (metadata, not credentials) but no explicit when/when-not guidance or alternative routing is provided.

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