disconnect

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

The description discloses that the tool disconnects and reverts to the default connection, which is a behavioral change. However, without annotations, it does not elaborate on potential side effects like closing existing queries or impacting other parts of the system.

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 a single, clear sentence that conveys all necessary information without any extraneous words. It is efficiently front-loaded.

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 (no parameters, no output schema), the description is complete. It explains the action and the result, and the sibling tool names provide additional context for understanding its role.

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 schema description coverage is 100%. No parameter information is needed, and the description adds no extra parameter semantics, which is appropriate. Baseline 4 for zero parameters.

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 description clearly states the verb 'Disconnect', the resource 'current runtime database', and the outcome 'revert to default environment-configured connection'. It distinguishes itself from sibling tools 'connect' (opposite action) and 'query' (different operation).

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 to use (when you want to disconnect and revert to default), but does not explicitly state when not to use or provide alternative tools. Given the siblings, context is implied but not explicit.

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