native_adbd_status

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

The description indicates a read-only operation, which implies no destructive side effects. However, without annotations, it carries the full burden and offers no additional behavioral details such as required permissions, rate limits, or what exactly 'status and environment' entails.

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 extremely short (one sentence) but lacks critical information. Conciseness is achieved at the cost of completeness, making it under-specified for effective tool selection.

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?

With 4 parameters, no schema descriptions, and no annotations, the description is inadequate. It does not explain the return format (though an output schema exists), nor does it provide enough context for correct use.

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 input schema has zero description coverage for its four parameters (login, target, http_port, name_type), and the tool description provides no hints about their meaning or usage. Users must infer from names alone, which is insufficient.

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 reads the status and environment of the native SteamOS adbd.service, using the verb 'Read' and specifying the resource. While it is distinct from sibling tools like adb_devices or adb_connect_lepton_usb, it does not explicitly differentiate itself, but the purpose is clear enough.

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?

No guidance is provided on when to use this tool versus its many sibling tools (e.g., adb_devices, adb_doctor). There is no mention of prerequisites or context for usage.

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