get_configured_databases

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

With no annotations, the description carries the full burden of behavioral transparency. The word 'List' implies a read-only operation, and the description mentions the return fields (id, name, engine), which gives some indication of output. However, it does not disclose potential limitations like permissions, pagination, or what happens if no databases are found. For a simple list tool, this is acceptable but minimal.

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 a single, concise sentence that is front-loaded with the action ('List all databases') and includes the key return fields in parentheses. Every word serves a purpose, with no unnecessary detail or restating of the tool name.

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 zero-parameter list tool with no output schema, the description provides complete context: it states the scope ('all databases configured in Metabase') and the fields returned (id, name, engine). This fully covers what the agent needs to know to invoke and interpret the tool.

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?

This tool has zero parameters, so there is no parameter information to convey. The baseline score for a zero-parameter tool is 4, and the description need not explain anything further. The schema is empty and coverage is trivially 100%.

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 it lists all databases configured in Metabase, with the specific fields returned (id, name, engine). The verb 'List' and resource 'all databases configured in Metabase' make it specific and unambiguous. However, it does not explicitly distinguish from the sibling tool get_database_metadata, which might retrieve details for a single database, so it doesn't fully earn a 5.

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 like get_database_metadata. It simply states what it does, leaving the agent to infer usage from the tool name and sibling context. There is no explicit when-to-use or when-not-to-use information.

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