list_databases

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

With no annotations, the description covers the return format, key usage, and filter behavior. It lacks info on permissions or caching, but is sufficient for a simple listing tool.

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 sentences plus a concise parameter note. Front-loaded with purpose, then return info, then key insight, then parameter detail. No extraneous content.

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 no output schema, the description provides return format. It covers the essential details for using the tool. Could mention scope (all databases accessible to user) but still adequate.

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 schema provides no parameter description (0% coverage). The description fully explains the filter parameter: optional, case-insensitive regex applied to key, host, or path, and default behavior when omitted.

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 action (list) and the resource (all servers and databases), and differentiates from siblings by specifying the return structure and the critical 'key' field used by other tools.

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 explains that omitting filter lists all, and provides details on filter usage (regex, case-insensitive). It does not explicitly mention when not to use or alternatives, but context makes its purpose distinct.

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