disconnect

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

With no annotations, the description carries the full burden. It does disclose one genuinely useful behavioral trait — that an in-progress sampling session is stopped first — which is an important side effect. However, it says nothing about error behavior (e.g. disconnecting when not connected), resource cleanup, or reconnect requirements.

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?

A single short sentence with the action front-loaded and the side effect parenthetically appended; nothing is wasted. It is arguably too terse for a state-mutating operation, but it is 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?

For a zero-parameter, annotation-free tool with no output schema, the description covers the core action and the key side effect (stopping sampling). It omits what state results after disconnection and whether the call is idempotent or errors when already disconnected.

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 takes zero parameters, so there is nothing for the description to add; baseline for a no-parameter tool is 4. The schema is vacuously complete.

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?

States a specific verb and resource: disconnecting the serial port. It is a clear, unambiguous action, but it never differentiates itself from the sibling 'connect' or explains how it relates to the capture/sampling siblings it interacts with.

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?

Usage is only implied by the tool name; there is no explicit statement of when to use it versus alternatives such as 'connect', nor any prerequisites or exclusions. The parenthetical hints at the sampling context but does not give selection guidance.

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