hex-list-data-connections

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

No annotations are provided, so the description carries the full behavioral burden. It states the read intent but says nothing about pagination behavior (despite after/limit params), result ordering defaults, or that results may be truncated, which matters for a list tool.

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?

A single front-loaded sentence with no filler. It is efficiently written, though its brevity comes at the cost of the missing guidance noted elsewhere.

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 4-parameter list tool with no annotations and no output schema, the description is too thin: it omits pagination, sorting semantics, and any indication of the shape or volume of returned connections.

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?

Four parameters exist with 0% schema description coverage and the description mentions none of them. after, limit, sortBy (CREATED_AT only), and sortDirection (ASC/DESC) are left entirely unexplained in both schema and description, so the agent cannot tell how to page or sort results.

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?

Clear verb+resource ('List all data connections') and scope ('configured in the Hex workspace'), so the agent knows this is a read-only enumeration of connections. However, it does not distinguish itself from the near-named sibling hex-get-data-connection (single fetch) or hex-create-data-connection, leaving differentiation to inference.

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?

No when-to-use guidance and no mention of alternatives such as hex-get-data-connection for a single record. The agent must infer that this is the bulk counterpart to the get sibling.

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