reconnect

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the force disconnect and re-login behavior, but does not disclose potential side effects (e.g., interrupting ongoing operations, requiring authentication, failure modes, or what happens if no userid was set). This is a significant gap for a session-management tool that could affect system state.

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 concise sentence that immediately conveys the core action and a key conditional behavior. It is front-loaded and contains no extraneous information. Efficient and well-structured.

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?

While the output schema exists (which covers return values), the description lacks important contextual details such as prerequisites, side effects, and typical use cases. Given the sibling set includes connect, login, and disconnect, the tool's role as a combined reset is implied but not fully explained. The description is adequate for a trivial tool but misses opportunities to clarify when to use it.

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 schema is empty. The baseline for 0 params is 4, as no parameter explanation is needed. The description adds behavioral context beyond the schema, which is appropriate. There is no parameter-related ambiguity.

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 tool's action: 'Force a disconnect + reconnect.' It also adds a specific behavior about re-logging in if a userid was previously set. This distinguishes it from plain connect or disconnect siblings, though it doesn't explicitly name them. It is specific enough for an agent to understand the primary function.

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 like calling disconnect followed by connect. It does not mention prerequisites, scenarios where this is preferred, or when it should be avoided. The 'Force' hint implies a reset, but the lack of explicit usage context leaves the agent to infer.

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