disconnect

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

With no annotations, the description carries the full burden of disclosing behavior. It only says 'Disconnect from server' without explaining side effects, whether the server is removed (unlikely, as delete_server exists), idempotency, or error behavior. The parameter description mentions the 'disconnect all' behavior, but that is in the schema, not the main description, and no broader transparency is provided.

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, front-loaded sentence with zero filler. It clearly states the core action in minimal words, earning full marks for conciseness.

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?

Despite the simplicity of the tool (one optional parameter, no output schema), the description is too sparse. It lacks usage context, safety/behavioral details, and differentiation from related tools. For a tool that can disconnect all servers, such potential impact warrants more explanation.

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?

Schema description coverage is 100% for the single parameter (server_id), which already explains the meaning and the 'leave empty to disconnect all' behavior. The tool description adds no additional parameter context, so the 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?

The description 'Disconnect from server' clearly states the action (disconnect) and the resource (server), which distinguishes it from siblings like connect and quick_connect. However, it does not mention the ability to disconnect all servers or a specific server, which is a scope detail only revealed in the parameter description.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no context about the connection lifecycle. It is implied by the name that this is the inverse of connect, but the description itself offers no explicit usage instruction or exclusions.

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