list_adb_features

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

The description asserts 'Read-only' while the annotations declare readOnlyHint=false, which directly conflicts with the structured safety signal an agent relies on to decide whether a write may occur. No other behavioral context (permissions, side effects, scope) is provided to resolve the ambiguity.

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 short, front-loaded sentences with the core action first and the read-only claim second. Nothing redundant or padded.

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 simple two-parameter list tool with complete schema coverage and no output schema, the description covers purpose but skips any indication of return shape or what identity assumptions the fingerprint data carries. Adequate but with clear gaps, and the read-only/mutation ambiguity hurts completeness.

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 description coverage is 100%, so the serial format and the analysis_project_id retention semantics are already fully documented in the schema. The description adds nothing about either parameter, so the baseline 3 applies.

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 names a specific verb and resource ('List the device's declared hardware and software features') and grounds it in a concrete ADB command (`pm list features`), so the agent knows exactly what is returned. It does not distinguish this from adjacent ADB siblings such as inspect_adb_device or list_adb_packages, which keeps it out of the top band.

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?

It gives a purpose context ('for device fingerprinting'), which implies when the tool is worth calling, but there is no explicit when-not guidance and no named alternative for overlapping device-introspection needs.

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