adb_connect

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

No annotations provided; description mentions the prerequisite but fails to disclose possible side effects (e.g., dropping existing connection) or error handling. Adequate but could be more transparent.

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 concise sentences with no redundant information; main purpose is front-loaded and every word adds value.

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 simple connect tool with one parameter and no output schema, the description covers purpose and prerequisites adequately. Could mention return value or connection status, but not necessary.

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?

Only one parameter 'host' with schema description providing examples. Description adds no additional semantic meaning beyond the schema, so 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?

States 'Connect to a device over WiFi/TCP' with clear verb and resource, and adds prerequisite details distinguishing it from siblings like adb_pair or adb_tcpip.

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?

Explicitly says when to use (WiFi/TCP connection) and specifies prerequisites (must be paired or TCP/IP enabled), though does not explicitly state when not to use or name alternatives.

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