List databases

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

No annotations are provided, so the description must disclose behavioral details. It only mentions 'optional pagination and filters' without explaining the default behavior, whether secrets are returned (showSecrets parameter), what 'summary' affects, or any side effects. This is insufficient for the agent to know what to expect.

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 sentence with no redundancy, getting straight to the point. It is concise and easy to parse, though its brevity sacrifices essential detail.

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 tool with 5 parameters, no schema descriptions, no annotations, and no output schema, this description is far from complete. Critical aspects like the meaning of 'type', 'summary', and 'showSecrets' are entirely absent, leaving the agent without enough information to invoke the tool 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?

Schema description coverage is 0%, meaning the parameters (type, limit, offset, summary, showSecrets) have no documentation. The description only groups them as 'pagination and filters' but fails to explain any individual parameter's meaning or purpose, leaving all five parameters opaque.

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 ('databases'), which distinguishes it from sibling tools like listApplications or listDeployments. However, it lacks specificity about the scope (e.g., across projects or environments) and does not elaborate on the types of filters, leaving some 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?

The phrase 'with optional pagination and filters' implies a use case where you need a paginated or filtered list of databases, but there is no explicit mention of when to prefer this over alternatives like getDatabase or listResources. No exclusions or alternative tools are named.

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