adb_at_send

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

With no annotations provided, the description adds value by stating root requirement and response capture. However, it lacks details on potential side effects, error behavior, or rate limits, leaving gaps in transparency for a tool with no annotations.

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 that front-load the core action and requirement, followed by actionable guidance. No filler or redundant information.

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?

Provides essential context (root, port detection, response capture) but lacks details on response format, error handling, or safety checks. Given the tool's simplicity and many siblings, it's mostly complete but could be improved.

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 schema covers all 5 parameters with descriptions. The description adds minimal extra context (e.g., port auto-detection, timeout ranges). Given 100% schema coverage, baseline is 3, and the description is adequate but not enhanced.

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 'Send a single AT command to the modem and capture the response', specifying the verb, resource, and output. It distinguishes itself from siblings like adb_at_batch for batch commands and adb_at_detect for port detection.

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 mentions 'Requires root' and suggests using adb_at_detect for finding the correct port or specifying manually. This provides clear context on prerequisites and a recommended alternative, though it doesn't explicitly cover when not to use.

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