adb_at_detect

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

Discloses root requirement but fails to describe what probing entails (e.g., if it modifies state, potential failures). Without annotations, description should provide more detail on behavior.

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?

Three concise sentences covering action, identification, requirement, and return. No unnecessary 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?

Adequately covers key aspects for a simple detect tool. Could mention possible return format or error cases, but not critical for functionality.

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?

Parameter 'device' is described in schema, and description adds no extra meaning. Schema coverage is 100%, so baseline 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?

Description clearly states auto-detect, identifies chipset families, probes paths, requires root, and returns first responding node. Distinguishes from siblings like adb_at_probe by focusing on detection vs. probing.

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?

Implies when to use (need to detect AT node) but lacks explicit when-not-to-use or alternatives. Does not compare with adb_at_probe or other related tools.

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