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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description still adds value beyond them: it explicitly says the data is permanently destroyed and imposes a human-in-the-loop confirmation (the caller must not fill in confirmDatabaseName on the user's behalf), which no annotation conveys.

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?

Three short sentences, front-loaded with the irreversible outcome. Each sentence carries information, though the description is terse enough that it leaves some behavioral questions (prerequisites, async completion) unaddressed.

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, no-output-schema mutation tool this covers the essentials (permanence, data loss, human confirmation, and the force behavior is in the schema), but it omits notable operational context: whether the database must first be detached or snapshotted, and whether deletion is synchronous or asynchronous.

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 67%: force and confirmDatabaseName are documented in the schema, and the description usefully reinforces that confirmDatabaseName is the user-typed name. managedDatabaseId has no description anywhere, but its meaning is self-evident. The description roughly matches the schema rather than substantially extending it.

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?

States a specific verb+resource ('delete a managed database instance') and the adverb 'Permanently' distinguishes it from the sibling nexusai_managed_db_detach and snapshot/restore tools. An agent can tell that this is irreversible removal rather than detachment without opening the schema.

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?

Usage is implied (this is the tool for permanently removing a database), and it carries one genuine usage rule: the person must type the name themselves. However, it never names alternatives such as nexusai_managed_db_detach or snapshotting first, so the when-to-use-vs-sibling decision is left to inference.

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