list_databases

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

No annotations exist, so the description must carry the full behavioral burden. It only states 'List all databases in ClickHouse' and provides no additional context about read-only nature, performance, pagination, or error behavior. Minimal disclosure beyond the obvious.

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?

One short sentence with no filler. Every word adds meaning: 'List', 'all', 'databases', 'ClickHouse'. Perfectly concise and front-loaded.

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 simple listing tool with no parameters, no output schema, and simple siblings, the description is nearly complete. It covers the core purpose. It could optionally mention whether system/internal databases are included or specify output format, but these are minor gaps. Adequate for an agent to invoke 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 schema coverage is trivially 100%. By rule, baseline for 0 params is 4. The description adds no parameter-specific meaning, but none is needed. It correctly implies the operation takes no arguments.

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?

Description uses specific verb 'List' and resource 'databases' scoped to ClickHouse. It clearly distinguishes from sibling tools like list_tables by naming the resource type. No ambiguity.

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?

Usage is implied by the description and tool name: use this when you need all databases in ClickHouse. However, it does not explicitly state when not to use it or mention alternatives such as list_tables for tables. No exclusions are given.

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