device_select

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

No annotations are provided, so the description carries the full burden. It does not disclose what 'select' means in terms of state changes, error behavior if the serial is invalid, or whether authorization is checked. Minimal information is given beyond the operation name.

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 a single sentence with no unnecessary words, directly conveying the action and key constraint. It is appropriately concise.

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?

The tool is simple with one parameter, but the description lacks behavioral details such as side effects (does selecting change the active device for all subsequent commands?), error handling, and usage context relative to siblings. This makes it incomplete for an agent to fully understand the tool's role.

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 schema only defines 'serial' as a string with length constraints. The description adds useful semantics: 'exact' indicates an exact match requirement and 'authorized' suggests only authorized devices are selectable. However, it does not explain how to obtain a serial or what makes a device authorized, so partial compensation for 0% schema coverage.

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 action ('Select') and the resource ('authorized Android device') with a specific qualifier ('by exact serial'). It distinguishes itself from sibling tools like device_list and device_info by indicating a selection action rather than listing or querying information.

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?

There is no guidance on when to use this tool versus alternatives, no mention of prerequisites (e.g., need to call device_list first to see available serials), and no exclusions. The context of being a selection step is implied but not stated.

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