Delete website database user

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

Annotations already provide destructiveHint=true and idempotentHint=true, but the description adds valuable context: it clarifies the operation is permanent, revokes all access, and explains the idempotency behavior in practical terms (deleting a non-existent user succeeds without error). This goes beyond what the annotations alone convey.

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 three short sentences that are front-loaded with the core action and consequence, followed by the idempotency note. Every sentence earns its place; there is no redundant or filler content.

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 simple, three-parameter delete operation with no output schema, the description plus annotations are sufficient for an agent to invoke it correctly. It covers what is deleted, the scope, destructiveness, and idempotency. No critical behavioral or scoping information is missing.

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 100%, so the parameters are already documented in the schema. The description itself adds no extra parameter-level guidance, leaving the baseline at 3. The schema's references to the list-databases endpoint are the primary source of semantic meaning.

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 specific verb 'Permanently deletes' and the resource 'database user from an Agency Plan website database', which distinguishes it from sibling tools like deleteWebsiteDatabaseV1 that delete the whole database. It also names the consequence ('revoking all access it had'), leaving no ambiguity about what the tool does.

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 when to use the tool (when you need to remove a database user from an Agency Plan website database) but does not explicitly discuss alternatives, exclusions, or when not to use it. For example, it does not contrast with deleting the entire database or with other user-management operations.

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