connect_flight_controller

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

No annotations are provided, so the description carries the full burden. It mentions connection via USB/serial but fails to disclose important behaviors: whether the connection is persistent, if it disconnects other sessions, timeout behavior, error states, or required permissions (e.g., serial device access). This is insufficient for a connection-oriented tool.

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 extremely concise: two sentences with no filler. Every sentence adds value—the first defines the action, the second provides a prerequisite step. It is well-structured and easy to parse.

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 moderate complexity (connection tool), the description covers the basic action and a prerequisite but lacks information about return values (e.g., connection handle, status), expected side effects (e.g., if a previous connection is terminated), and error handling. With no output schema, more context on what to expect after connecting would be beneficial.

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 input schema covers 100% of the parameters with decent descriptions (port with examples, baud_rate with default). The description does not add any additional meaning beyond what's in the schema, so a baseline score of 3 is appropriate.

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 ('Connect'), the resource ('Betaflight flight controller'), and the medium ('over USB/serial'). It is specific and distinguishable from siblings like disconnect_flight_controller and reconnect_flight_controller, and it also mentions a prerequisite tool (list_serial_ports).

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 advises to use list_serial_ports first to find the correct port, providing clear contextual guidance. However, it does not specify when not to use this tool or mention alternatives, such as reconnect_flight_controller if already connected.

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