List databases

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

The annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds context about pagination and filters, but does not disclose important behaviors such as whether secrets are hidden by default, what 'summary' means, or how filters affect results. This adds a little beyond annotations but not rich 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?

The description is a single concise sentence with no wasted words, and it is front-loaded with the core action. However, it is arguably too sparse given the tool's parameter complexity, so it sacrifices substance for brevity.

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?

The tool has no output schema, five parameters with no descriptions, and nine sibling tools. The description does not explain the return value, the meaning of 'filters', the behavior of 'showSecrets', or how this list differs from other list tools. This is insufficient for an agent to fully understand and correctly invoke the tool in all intended scenarios.

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?

With schema description coverage at 0%, the description must compensate for the five undocumented parameters. It only provides the generic phrase 'optional pagination and filters', which vaguely maps to limit/offset and type, but leaves 'summary' and 'showSecrets' entirely unexplained. The description adds minimal semantic value beyond the schema's parameter names and types.

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 resource ('databases'), which is specific and unambiguous. However, it does not explicitly distinguish itself from sibling tools like 'getDatabase' or other list tools, though the plural form and mention of pagination/filters hint at a collection-level operation.

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?

No guidance is provided on when to use this tool versus alternatives such as 'getDatabase' or 'databaseBackups'. The description only mentions optional pagination and filters, implying a standard listing use case, but it lacks explicit context, prerequisites, or alternative recommendations.

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