get_device_info

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the agent knows the operation is safe. The description adds value by enumerating the exact data points retrieved and the nuance about the device self-reporting as an emulator. No side effects or failure modes are disclosed, but for a pure getter this is adequate.

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, information-dense sentence that front-loads the verb 'Read' and lists all returned fields without extraneous wording. Every clause earns its place, making it concise and well-structured.

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 one-parameter getter with no output schema, the description lists all return data points, which serves as an implicit specification of the response content. The schema covers the device_serial behavior, including active device fallback, so the overall context is complete enough for an agent to invoke the tool correctly.

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 one optional parameter (device_serial) with a complete description covering 100% of the schema. The tool description adds nothing about parameter semantics beyond what the schema already states, so the baseline of 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 clearly states the tool reads specific device attributes (model, manufacturer, Android version, SDK, screen info, emulator status) using a precise verb ('Read') and a defined resource. It distinguishes from sibling tools like list_devices by focusing on properties of a single target device rather than device discovery.

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 use when device details are needed but does not explicitly state when to prefer this tool over alternatives or provide exclusion conditions. Among the many sibling tools, no direct comparison or alternative guidance is given, so the agent must infer applicability.

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