adb_modem_logs

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

Discloses that 'dmesg' requires root, but provides no further detail on behavior such as partial output when root is missing, timeouts, or how logs are combined. With no annotations, the description partly fulfills transparency but leaves gaps in expected output 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?

A single, well-structured paragraph that front-loads the main purpose and adds key details without extra fluff. Every sentence provides value.

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?

Covers purpose, log sources, root requirement, and use case. Lacks output format details (e.g., whether logs are concatenated or separate) since no output schema, but for a log capture tool this is adequate.

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%, so the description does not need to repeat parameter details. However, it does not add extra meaning beyond the schema, such as which log source each parameter affects. Baseline score of 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?

Specific verb 'Capture' with clear resource 'modem/baseband-related logs'. Names three distinct sources (RIL logcat, telephony framework logs, kernel dmesg). Clearly distinguishes from sibling tools like adb_logcat (general logcat) and adb_telephony (telephony state).

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 states usefulness for 'radio diagnostics and tracing baseband-framework communication', providing context for when to use. Does not explicitly mention when not to use or list alternatives, but the specificity of the task implies appropriate use cases.

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