list_connections

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

readOnlyHint=true already covers the safety profile, and the description does add one genuine behavioral fact — that results come back in a HAL-style envelope with a 'first' href and total_count, implying cursor-based paging. However that fact is stated cryptically with no explanation of what the envelope contains or how to follow pagination, and it discloses nothing about scoping, filtering, or errors.

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?

It is short, but the opening clause "Native envelope confirmed live" is verification chatter that consumes the front-loaded position with no actionable meaning. Brevity here comes from under-specification rather than economy.

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 four-parameter, project-scoped list tool with no output schema and zero schema coverage, the description should state what is listed, how pagination is driven, and how filtering works. None of that is present, so an agent has almost nothing to call it correctly beyond guessing from parameter names.

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% across four parameters (limit, cursor, project_id, name_contains), so the description carries the full burden and fails: it only obliquely hints at cursor pagination via 'first: {href}'. It says nothing about what project_id scopes to, what name_contains filters, or what limit defaults to.

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 never states that this tool lists connections. Instead it describes a response envelope shape ("{resources: [], first: {href}, total_count}") and compares pagination styles to other tools, so an agent cannot determine the verb or resource from the text alone — it would have to infer everything from the name.

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 guidance, no mention of the sibling alternatives that matter here (list_connection_types, get_connection, list_projects), and no conditions under which this tool should or should not be chosen. The only comparison drawn is about pagination shape, which does not help select the tool.

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