ecp_postgres_create_database_user

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

With no annotations, the description carries the behavioral burden. It usefully discloses that the submitted db_username is automatically prefixed, which is non-obvious. However, it does not mention default privileges, failure behavior if the user already exists, or what the response contains.

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 short sentences, with the core action first and the key behavioral caveat second. Every word earns its place; there is no filler or repetition.

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 two-parameter create operation with no output schema, the description is largely complete: it identifies the operation, the required inputs, and the critical prefix behavior. The lack of details about password constraints or post-creation privileges is a minor gap at this complexity level.

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 description adds meaningful semantics for db_username by explaining the automatic prefix, which the schema does not convey. The password parameter receives no added explanation, but its purpose is clear from its name and string type; the compensation is partial rather than complete.

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 states a specific action (Create) and resource (an additional Postgres user), and the word 'Postgres' plus 'user' clearly separates it from sibling tools that create MySQL/MSSQL/Mongo users or Postgres databases. 'Additional' also signals it is not the account's initial user.

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 'additional Postgres user' gives clear context: use this when an extra user is needed, not when creating a database or managing an existing user. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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