pg_drop_role

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

No annotations are provided, so the description carries full burden. It mentions 'Request role deletion' and 'short-lived confirmation token', suggesting a two-step process, but it does not specify whether the role is immediately deleted, what happens if the token expires, or any permission requirements. This leaves significant behavioral ambiguity for an agent.

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 sentence of 10 words, which is concise. However, it could be expanded slightly to include more behavioral details without becoming verbose.

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 that this tool has no output schema, no annotations, and only one parameter, the description should provide more context about the confirmation token mechanism and lifecycle. The current text leaves uncertainty about the deletion's finality and the agent's next steps.

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 defines one parameter 'role' with type string and minLength 1, but has 0% schema description coverage. The tool description does not elaborate on the role parameter, so an agent must infer its meaning from the tool name and context. Adding a description would improve clarity.

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 action ('Request role deletion') and the resource ('role'), and it distinguishes itself by mentioning the unique outcome of returning a short-lived confirmation token, which differentiates it from sibling tools like pg_drop_database or pg_create_role.

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 provides no guidance on when to use this tool versus alternatives, such as when a two-step deletion process is needed or when to use pg_confirm_task. There are no prerequisites or exclusions mentioned.

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