list_connections

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'List all connections' implies a read-only operation, but it doesn't specify whether this requires authentication, what the output format is (e.g., paginated list), or any rate limits. For a tool with zero annotation coverage, this is a significant gap in transparency.

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 extremely concise at three words, with no wasted text. It's front-loaded with the core action ('List all connections'), making it easy to parse quickly. This efficiency is appropriate for a simple-sounding tool, though it may sacrifice clarity.

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?

Given the complexity (3 parameters with no schema descriptions, no annotations, and no output schema), the description is incomplete. It doesn't explain the tool's behavior, parameter usage, or output, leaving the agent with insufficient context to use it effectively. For a list tool with undocumented parameters, more detail is needed.

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 input schema has 3 parameters (limit, offset, order_by) with 0% schema description coverage, meaning none are documented in the schema. The description 'List all connections' adds no information about these parameters—it doesn't explain what 'limit' controls, how 'offset' works for pagination, or what 'order_by' values are acceptable. This fails to compensate for the low schema coverage.

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 'List all connections' clearly states the verb ('List') and resource ('connections'), which is better than a tautology. However, it lacks specificity about what 'connections' are in this context (e.g., Airflow connections) and doesn't distinguish from sibling tools like 'get_connection' (which fetches a single connection) or 'create_connection' (which creates one). This makes it vague compared to alternatives.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'get_connection' for retrieving a specific connection or 'create_connection' for adding new ones. There's no context about prerequisites, such as authentication or permissions, leaving the agent to infer usage from the tool name alone.

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