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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the description's added value is the non-obvious failure semantics: without CASCADE a dependent extension survives the call, and the reason surfaces via get_database. It also names the required scope (databases.write), which the annotations do not convey. It does not describe the success return, keeping it below 5.

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 sentences, zero filler: the destructive no-CASCADE behavior is front-loaded and the permission scope is a compact trailing note.

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, three-param tool with no output schema, the description covers the key risk (dependent objects block the drop), where to diagnose it, and the required scope. Only the success-path outcome is left implicit.

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%, so the schema does most of the work, but the description adds no meaning for any of the three params — notably 'extension' has no schema description at all and the description never mentions it or the naming rules for it. Baseline 3 is appropriate.

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 and resource ("Drops the extension") with an important qualifier (no CASCADE), which clearly marks the inverse of the enable_extension sibling. It stops short of naming that sibling explicitly, but the operation is unambiguous.

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 this tool applies by describing the dependency case and pointing to get_database for diagnostics, but it never states explicit when-to-use/when-not conditions or names enable_extension as the counterpart operation.

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