list_databases

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

The annotation readOnlyHint=true already communicates that this is a safe read operation. The description adds context like 'check connection status' and 'get an overview,' but doesn't disclose additional behavioral details such as pagination, response size, or any rate limits. This is acceptable for a simple list tool but not exceptional.

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 two sentences with the primary action front-loaded. The first sentence says exactly what it does, and the second sentence adds practical use cases without redundancy. Every word adds 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?

For a parameterless read-only list tool with an output schema available, the description is sufficiently complete. It states the scope (all database connections), the purpose (discovery, status, overview), and no further context is needed for an agent to use it correctly.

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 has zero parameters, so the schema needs no explanation. The description's word 'all' confirms that no filtering is possible, which aligns perfectly with the empty input schema. This meets the baseline for parameterless tools.

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 clearly states the tool retrieves all database connections in Metabase, using the specific verb 'Retrieve' and naming the resource. It distinguishes itself from siblings like get_database (single database) and list_tables (tables within a database) by explicitly covering all connections.

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 clear use cases: discover available data sources, check connection status, or get an overview. While it doesn't explicitly mention when not to use it or compare to alternatives, the context is strong enough for typical selection.

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