adb_runtime_audit

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

With no annotations supplied, the description carries the full burden, and it does handle the most important trait by declaring the operation read-only and that it 'Makes no device changes.' Beyond that it is silent on runtime cost, whether root/SELinux probes touch privileged paths, partial-failure behavior, and how results are surfaced — all material for a tool that fans out across a dozen subsystems.

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 tight sentences, front-loaded with the verb and scope, and the safety guarantee is placed last as a clean closing clause. The long domain enumeration is dense but each item genuinely bounds scope, so little is wasted.

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 zero-configuration audit tool with no output schema and no annotations, the description should at least hint at the shape of the result (per-check pass/fail, aggregate verdict) since nothing else communicates it. It is complete on scope and safety but incomplete on what the agent gets back and how to interpret it.

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?

There is a single optional 'device' parameter and schema description coverage is 100%, so the schema already defines it fully. The description adds no device-selection semantics (e.g., default device behavior when omitted, multi-device handling), which is the only place it could have added value here.

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 a specific verb ('Run') and a clearly scoped resource ('unified, read-only DeepADB readiness audit') and enumerates the eleven domains covered, so an agent knows exactly what ground it touches. It does not, however, name or contrast itself with the obviously overlapping siblings (adb_health_check, adb_device_info, adb_firmware_probe, adb_selinux_status), leaving the superset-vs-specialist relationship to inference.

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?

Usage is only implied: the 'readiness audit' framing signals a pre-flight/setup check, but there is no explicit when-to-use statement, no condition under which the narrower sibling tools should be preferred, and no prerequisites (device connection, root availability) given. The agent must infer placement in a workflow.

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