agency-hosting_deleteWebsiteDatabaseV1

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

With no annotations, the description carries the transparency burden. It discloses permanent destruction, all data and users affected, and idempotent behavior when the database does not exist. It could add response/error details, but the core destructive traits are explicit.

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 concise sentences front-load the primary action and add only the essential idempotency caveat. No filler or repetition of schema fields.

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 destructive two-parameter tool with no output schema, the description is complete: it explains scope, permanent data loss, users affected, and behavior on missing databases. It does not detail response semantics, but this is not essential given the schema and idempotency note.

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 coverage is 100% and both parameters already have clear descriptions, so the description adds little parameter-level meaning beyond specifying the database type as MySQL. This matches the baseline for high schema coverage.

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 the exact action: 'Permanently deletes a MySQL database and all its data from an Agency Plan website, including its users.' This uses a specific verb and resource and clearly distinguishes the website-scoped deletion from account-level database deletion.

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 clearly frames when this tool applies: deleting a MySQL database that belongs to an Agency Plan website. It does not explicitly contrast with account-level delete database siblings, but the scope is clear enough for selection.

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