Delete PostgreSQL User

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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds the API endpoint and context of the Postgres instance, but does not disclose side effects (e.g., cascading deletes, impact on existing connections). It provides marginal extra value beyond annotations.

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 no fluff. The title is front-loaded, and the description efficiently conveys purpose and API call. All sentences are necessary.

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?

With no output schema and 0% schema coverage, the description should explain parameters and return behavior. It does not mention success/error responses or confirm deletion. Incomplete for a delete operation.

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%. The description mentions 'with the provided ID' and the endpoint includes {username}, but it does not explain what postgresId or username represent (e.g., format, constraints). Fails to add meaning beyond the schema's property names.

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 'Delete PostgreSQL User' and specifies the action of deleting a user from a Render Postgres instance. It includes the API endpoint for precise context, distinguishing it from create or other delete tools.

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 usage guidance is provided. It does not specify prerequisites (e.g., user must exist) or when to avoid using this tool (e.g., if the user has active connections). Alternatives or when-not-to-use are not mentioned.

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