reconnect_flight_controller

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

No annotations are provided, so the description carries full burden. It discloses one key behavior ('Will disconnect any existing session first') but does not mention failure scenarios, whether it is a destructive operation, or any required permissions. The description adds some value but lacks full behavioral transparency.

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 three sentences, front-loaded with the primary action, followed by a use-case example and a behavioral note. Every sentence earns its place with no wasted words.

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 no parameters, no output schema, and no annotations, the description covers the essentials: what it does, when to use it, and a key behavior. It lacks details on what happens if there is no previous connection or on failure, but is otherwise complete for a simple tool.

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, so baseline is 4. The description explains that the tool uses the last connected port and baud rate, adding meaning beyond the empty input schema. It does not need to explain parameters, but the behavioral context is helpful.

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 action 'Reconnect to the last connected flight controller using the same port and baud rate.' It specifies the verb 'reconnect' and the resource 'flight controller,' and distinguishes itself from siblings like 'connect_flight_controller' by emphasizing it uses stored credentials and disconnects any existing session.

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 a clear use case: 'Useful after a reboot (e.g. following cli_save or reboot_flight_controller).' It also warns that it will disconnect any existing session, but does not explicitly state when not to use it or name alternative tools. However, the context is sufficient for an agent to infer appropriate usage.

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