pg_alter_role_attributes

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

With no annotations, the description carries the burden of behavioral disclosure. It only states that SUPERUSER is not supported, but lacks information on permissions required, side effects (e.g., immediate changes), error behavior, or whether the role must exist. Minimal disclosure.

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 concise (two sentences), but at the cost of missing essential details. It does not waste words, but it fails to provide necessary information for tool usage.

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 tool has 9 parameters, no schema descriptions, no output schema, and no annotations, the description is severely incomplete. It barely covers the tool's purpose and one constraint, leaving the agent without guidance on parameter usage, return values, or behavior.

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%, so the description must explain parameters. It provides no information about what each parameter (e.g., login, inherit, createdb) does. The agent cannot understand the meaning or correct usage of the 9 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 clearly states the verb 'Change' and the resource 'PostgreSQL role attributes', and adds a key constraint 'SUPERUSER is intentionally not supported'. This distinguishes it from siblings like pg_alter_role_password (which changes password specifically) and pg_create_role (which creates 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?

The description implies usage for non-password attributes and excludes SUPERUSER, but does not explicitly state when to use this vs alternatives. For example, it does not mention that for password changes, pg_alter_role_password should be used. No when-not or alternative tool references.

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