Delete account database

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

Annotations already mark this as destructive and not read-only. The description adds value by stating the deletion is permanent and that remote connections are also deleted, which is useful behavioral context beyond the 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 convey the core action, scope, and an important prerequisite with no wasted words. The destructive nature is front-loaded, and the constraint on the database name is placed immediately after.

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 two-parameter delete operation, the description covers the action, scope, and required input constraint. It does not describe return behavior or error cases, but no output schema exists and the annotations cover the safety profile.

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%, and the description repeats the 'full database name' requirement already present in the schema. It adds no additional meaning for the parameters, especially 'username', which remains generic in both places.

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 states a specific action ('permanently deletes') and resource ('a database and its remote connections'), which clearly identifies the tool's purpose. It also distinguishes itself from related siblings like deleting only a remote connection or deleting a website database.

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 a prerequisite for the database name but does not explain when to choose this tool over alternatives such as hosting_deleteDatabaseRemoteConnectionV1 or agency-hosting_deleteWebsiteDatabaseV1. No explicit when-to-use or when-not-to-use guidance is given.

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