ecp_postgres_list_db_users

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

With no annotations, the description carries the behavioral burden. 'List' implies a read-only operation and 'additional' hints at a subset of users, but the description does not disclose output format, what 'additional' excludes, or any account-level prerequisites. For a simple zero-parameter list tool, this is adequate but minimal.

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 filler. Every word adds meaning: 'additional', 'Postgres users', and 'on this account' all carry relevant scope information.

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 read-only listing tool with no output schema and no annotations, this description is largely sufficient for an agent to invoke it correctly. The main gap is that 'additional' is not formally defined and the return shape is not described, but the operation is simple enough that this is a minor omission.

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 input schema is empty, so there are no parameter semantics to clarify; the baseline for zero-parameter tools is 4. The 'on this account' phrase provides useful context without needing to document parameters.

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 resource ('additional Postgres users on this account'), which clearly distinguishes it from sibling tools like ecp_postgres_list_databases and ecp_postgres_list_privileges. The scope 'on this account' adds useful precision.

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 the additional Postgres users for the current account. However, it does not explicitly state when not to use it or mention any alternative tool, leaving usage guidance mostly to inference.

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