pg_create_role

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

With no annotations, the description bears full responsibility for behavioral disclosure. It discloses that SUPERUSER is not supported, but fails to mention other behavioral traits such as error handling, permissions required, or side effects. This under-disclosure leaves significant gaps.

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 very short (one sentence), which is concise but insufficient for a tool with 10 parameters. It front-loads the purpose but omits necessary details, making it under-specified for the complexity.

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?

Given the complexity (10 params, no output schema, no annotations), the description is severely incomplete. It does not cover return values, error conditions, or parameter usage, leaving the agent with inadequate context to use 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?

The input schema has 10 parameters with 0% description coverage. The tool description does not explain any parameter, such as 'role', 'login', or 'password'. It adds no semantic value beyond the schema structure, which is insufficient given the lack of schema descriptions.

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 'Create a PostgreSQL role', which is a specific verb and resource. The note 'SUPERUSER is intentionally not supported' distinguishes it from role creation tools that might allow SUPERUSER, and it differentiates from sibling tools that alter or drop roles.

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 explicit guidance on when to use this tool versus alternatives like pg_alter_role_attributes or pg_drop_role. The description only states what it does, not when or when not to use it.

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