hosting_deleteAccountDatabaseV1

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

The description discloses that the deletion is permanent and also removes remote connections. With no annotations, it provides crucial behavioral context about irreversibility and scope. Missing details like permissions or error handling, but adequate for the operation.

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 concise with two sentences. The first states the action and scope, the second provides a critical usage note. No unnecessary words, well-structured.

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 deletion tool, the description covers the action, scope, and a key prerequisite (correct name). It does not mention return values or error scenarios, but given the simplicity, it is reasonably complete.

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 already describes both parameters (username and name). The description adds value by clarifying that the 'name' parameter must be the exact full name from the list endpoint, which reinforces correct usage.

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 tool permanently deletes a database and its remote connections. It specifies the verb (delete) and resource (database), and includes a distinguishing constraint about using the full name from the list endpoint.

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 explicitly mentions that the database name must be the full name from the list databases endpoint, guiding the agent to fetch that first. It does not explicitly state when not to use it, but the constraint implies proper prerequisites.

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