release_port

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

With no annotations, the description carries the full burden and delivers: the side effect on servo state ('servos keep holding'), the lifecycle behavior ('reopens automatically on the next tool call'), and the reason the operation exists. It omits failure semantics — what happens if the port is already released or if a command is in flight.

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 short sentences, imperative and front-loaded with the action, followed by the state consequence and the auto-reopen behavior. Every clause carries information an agent needs.

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 lifecycle tool with an output schema available, the description covers action, side effect, and re-acquisition behavior. Only error/edge-case handling is absent, which is minor given the output schema can carry the result detail.

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 the schema-level baseline is 4. The description correctly implies no arguments are needed, and there is nothing further to disambiguate.

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 (close the serial port) with immediate scope ('now') and a concrete consequence ('servos keep holding'). No sibling tool in the list does anything similar, and the description makes that exclusivity obvious by naming the external consumers (GUI, flash.py) that need the port.

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?

Gives a clear trigger condition — release when the GUI or flash.py needs the board — which effectively says when to use it. It does not state exclusions explicitly (e.g., don't bother calling if you are about to make another tool call), though the auto-reopen note implies that.

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