adb_at_probe

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

No annotations provided, so description must cover behavioral traits. Only discloses root requirement. Does not mention whether the probe modifies modem state, is read-only, or triggers side effects. Lacks details on auth, rate limits, or destructive potential.

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?

Extremely concise: two sentences, first providing core purpose and specifics, second adding critical root requirement. No wasted words, front-loaded.

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?

Lists covered diagnostic areas but lacks output schema description. Agent knows what kind of data to expect (modem status, signal quality, etc.) but not the format or structure. For a probe tool, more detail on return format would be helpful.

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 coverage is 100% and description does not add value beyond schema descriptions. For port, schema already states 'auto-detects if omitted'. Device parameter is not elaborated. Overall, description does not enhance parameter understanding.

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?

Clearly states the tool runs a standard AT diagnostic probe and enumerates specific checks (modem identification, signal quality, network registration, SIM status, supported bands). Distinguishes from sibling AT tools like adb_at_send or adb_at_batch by being a composite 'probe'.

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?

Mentions 'standard' probe, implying routine diagnostic use, but does not explicitly state when to use this vs other AT tools or alternatives. No exclusion criteria or contextual guidance.

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