redash.list_connections

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

Discloses that URLs and API keys are never returned, an important security guarantee. No annotations exist, so description carries full burden; provides valuable behavioral context.

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 concise sentences; first states primary purpose, second adds critical behavioral detail. No superfluous text.

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?

Adequate for a simple list tool with no input schema and no output schema. Tells agent it will get connection IDs and a security guarantee. Could mention if other fields like names are returned, but not necessary.

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?

No parameters (baseline 4 since 0 params). Description adds meaning beyond empty schema by clarifying what is not in the output.

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?

Clearly states it lists connection IDs, and distinguishes from siblings by noting what is not returned (URLs, API keys). Siblings are query-focused, making this tool's purpose unique.

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?

Implicitly suggests use before tools requiring a connection ID; no explicit when-not or alternatives, but given the simple parameter-less nature, context is clear.

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