reconnect_last

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

There are no annotations, so the description carries the behavioral disclosure burden. It discloses that the tool reuses previous session settings and, importantly, handles the no-remembered-settings case by directing the user to `connect`. It could add a bit more about failure behavior or side effects of reconnecting, but for a zero-parameter convenience tool this is solid.

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 short and efficient, with the core purpose in the first sentence and supporting usage guidance plus fallback behavior in the following sentences. Every sentence earns its place with no redundant content.

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 low complexity, zero parameters, and existence of an output schema, the description covers what an agent needs: when to use it, what it does, and what to do if no previous session exists. There are no obvious gaps for correct invocation.

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 100% schema coverage, so the baseline is 4. The description adds useful context by naming what settings are remembered (port and baud rate), even though no input is required.

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 reconnects to the most recently used port/settings from a previous session, which is a specific action with a defined resource. It also distinguishes itself from the sibling `connect` by explaining the fallback condition, so an agent can tell them apart.

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 explicitly says it is handy at the start of a chat so the user doesn't have to repeat the port and baud rate. It also names the alternative (`connect`) and specifies the condition when that alternative should be used instead.

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