Connect Database

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

The description reveals that all connection settings come from environment variables only, and that calling again reconnects—beyond the idempotentHint annotation. It also discloses parameter exclusion, but doesn't cover failure 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?

Two sentences, front-loaded with the action and resource, then concise details on env vars and idempotency. No redundancy or filler.

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 zero-parameter connection tool with an output schema and idempotentHint annotation, the description covers connection mechanism, configuration source, and repeated-call behavior. Complete for the tool's complexity.

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?

With zero parameters and 100% schema coverage (empty schema), the description compensates by listing the exact environment variables used and explicitly stating no credentials are accepted, giving full meaning to the empty parameter list.

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 starts with specific verb 'Connects to MS SQL Server', clearly identifies the resource and distinguishes from disconnect/status/query siblings. It also specifies that no credentials are accepted as parameters, further clarifying scope.

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?

Implied usage as a prerequisite for MSSQL operations, but no explicit 'use when' or 'use connection_status instead' guidance. The description doesn't mention alternatives or when not to use it.

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