get_device_info

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

No annotations are provided, so the description carries the full burden. 'Read' indicates a non-destructive operation, but the description does not disclose potential behaviors like how it handles multiple connected devices or what the output structure is. While the schema mentions the device parameter, the description alone offers limited behavioral detail.

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, highly readable sentence that leads with the action and lists the key facts. It is optimally concise with no filler or redundant content.

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 and an output schema exists, so the description does not need to explain return values. It covers the core purpose adequately. A minor gap is the lack of explicit handling for the optional device parameter, but the schema provides that context.

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 description fully covers the single parameter (device), so the baseline is 3. The description does not add any additional parameter semantics beyond what the schema already provides, but no extra information is necessary given the high 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 specifies the exact action ('Read') and the resource ('device facts') along with a concrete list of attributes (model, manufacturer, Android version, resolution, density). This clearly distinguishes the tool from sibling action tools like tap or swipe.

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?

The description implies usage when device properties are needed, but it does not explicitly state when to use this tool over alternatives or mention any exclusions. The simple read-only nature makes the context clear, yet no direct guidance is provided.

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