adb_ota_check

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

With no annotations, the description must carry full behavioral transparency. It explains the comparison (what changes are detected) but omits details like whether the operation is read-only, prerequisites (e.g., saved fingerprint must exist), or failure modes. This is decent but incomplete.

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 concise at two sentences, front-loaded with the main action, and every sentence adds value. No wasted words or redundancy.

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 no output schema, the description should at least hint at return format (e.g., diff result or detection status). It also misses prerequisites (need saved fingerprint). For a simple comparison tool, it is adequate but not fully complete.

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% with clear parameter descriptions (fingerprintPath includes default behavior). The tool description does not add extra meaning beyond the schema, so baseline score of 3 applies per guidelines.

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 tool's purpose: comparing the current system state against a saved fingerprint to detect OTA updates, with specific components (build ID, security patch, etc.). This verb+resource specificity distinguishes it from siblings like adb_ota_fingerprint (saving) and adb_ota_history (historical checks).

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?

The description lacks any guidance on when or when not to use this tool versus alternatives like adb_firmware_diff or adb_ota_fingerprint. No usage context or exclusions are provided, leaving the agent to infer appropriate scenarios.

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