adb_connect_lepton_usb

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

With no annotations, the description must fully explain behavior. It states 'connect' and 'port forwarding' but does not disclose what the connection entails (e.g., whether it establishes a persistent tunnel, requires device authorization, or affects existing ADB connections). The specifics of the port forwarding mechanism are not detailed.

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 one sentence and 13 words, which is concise. However, the extreme brevity sacrifices necessary detail. It is front-loaded with the key action but lacks the completeness needed for a tool with two parameters and no annotations.

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 has 2 parameters, an output schema (not described), and no annotations, the description is insufficient. It fails to cover return values, preconditions, or the effect of the operation. The user or agent lacks critical context to use the tool correctly.

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?

Schema description coverage is 0% and the description does not mention the two parameters (local_port, remote_port). The user is left to guess their meaning and purpose. Even defaults are provided in the schema, but without explanation, the agent cannot determine how to appropriately set these ports.

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 verb 'Connect', the specific resource 'Steam Frame's Lepton Android container', and the method 'through USB ADB port forwarding'. It effectively distinguishes from sibling 'adb_connect_lepton_wifi' which uses a different connection method.

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?

No guidance is provided on when to use this tool versus alternatives like 'adb_connect_lepton_wifi' or when to avoid it. It lacks context on prerequisites, such as needing a connected USB device or having ADB set up, and does not mention any conditions for use.

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