ecp_postgres_list_databases

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

With no annotations and no output schema, the description carries the full behavioral burden. It clearly indicates a read-only listing operation scoped to the account, but it does not disclose what information is returned (names only versus metadata) or whether any filtering occurs.

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, front-loaded sentence with no wasted words. It states the action and scope efficiently, which is ideal for a simple parameterless list tool.

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 operation, the description provides enough context to invoke the tool correctly. A minor gap is that there is no output schema or mention of the return shape, but for a simple database listing this is not a major obstacle.

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 and the schema has full description coverage, so there is no parameter documentation burden for the description. The baseline of 4 applies for parameterless tools because schema and description leave nothing ambiguous about inputs.

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 uses a specific verb ('List') and a precise resource ('this account's Postgres databases'), making the operation clear. It also differentiates from sibling tools like ecp_mysql_list_databases or ecp_postgres_database_sizes by naming both the engine and the list action.

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 intended use is implied: call this when you need to enumerate the account's Postgres databases, rather than MySQL, Mongo, or MSSQL ones. However, there is no explicit guidance about when to prefer this over related Postgres introspection tools like ecp_postgres_database_sizes or ecp_postgres_list_columns.

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