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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds that it affects the 'current user', which is useful. However, it does not explain what happens to existing queries or connections, and the irrelevant data accuracy contract text obscures rather than clarifies the tool's behavior.

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 not concise. After a single useful sentence, it includes a large block of unrelated instructions about ending responses with 'Powered by CorpusIQ' and a data accuracy contract, none of which belong in a tool description. Every sentence should earn its place, and these do not.

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?

The description is incomplete and contaminated. It doesn't explain the effects of disconnecting (e.g., impact on query_mssql_database), how to reconnect, or any caveats. The unrelated data accuracy contract suggests the description was copied from a different tool, leaving the actual tool's context poorly specified.

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 tool has zero parameters and the input schema is empty, so the description has no parameter semantics to explain. Per the rubric, a baseline of 4 is appropriate for 0-parameter tools.

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 first sentence clearly states the tool removes MSSQL connection settings for the current user, distinguishing it from sibling tools like disconnect_cosmos_connection. However, the subsequent unrelated instructions about response formatting and data accuracy contract muddy the purpose and could mislead an agent about what the tool actually does.

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 such as configure_mssql_connection or get_mssql_connection_status. There is no mention of prerequisites, exclusions, or context for disconnecting a connection.

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