✓ SAFE: Close database connection and free resources. Doesn't affect file.

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

The description discloses the action (close connection, free resources) and its non-destructive nature. However, it omits details like whether it commits pending transactions, idempotency, or error behavior. Annotations are absent, so the description carries full burden but only partially fulfills it.

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 extremely short with no fluff, but it repeats the title verbatim. It is concise but could be slightly more informative without losing brevity.

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 tool's simplicity and lack of output schema, the description is adequate but not thorough. It doesn't state prerequisites (e.g., database must be open) or consequences, which would improve completeness.

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 optional database_name parameter is not mentioned in the description. With 0% schema description coverage, the description should explain its purpose (e.g., which connection to close). The omission leaves the agent guessing.

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?

Tautological: description restates name/title.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., after transactions, before closing app). The description only asserts safety, not context or exclusions.

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