close_database

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

With no annotations present, the description carries full behavioral burden and does so well. It discloses that other clients are not disrupted, that orphaned execution is cancelled on final lease, that the call blocks until closing finishes, and that GUI databases are never affected.

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 dense sentences with no filler. The main purpose is front-loaded, followed by key edge-case behavior and an exclusion. Every sentence adds meaningful information.

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?

Given the low parameter complexity, full schema coverage, and existing output schema, the description is sufficient. It covers purpose, side effects, blocking behavior, lease semantics, and GUI exclusion without needing to explain return values.

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 only parameter, instance_id, is fully documented in the input schema with its default and behavior when omitted. The description adds no extra parameter detail, but the schema already provides complete coverage, so 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?

Description states a specific action: 'Release this MCP server's handle' rather than closing a database outright. This clearly distinguishes close_database from siblings like open_database, save_database, list_databases, and reference.

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?

Provides clear context on when to use the tool: releasing a handle, potentially on a final lease, and explicitly excludes GUI databases with 'GUI databases are never closed here.' It does not name a specific alternative tool for GUI database closing, but the when-not condition is clear.

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