get_device_info

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

With no annotations provided, the description carries the full behavioral burden. It does disclose the output format (JSON string) and the precondition that the device must be 'connected', which is genuinely useful context, but it says nothing about failure modes when no device is attached or whether it is a safe read-only call.

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 sentences with no filler: the purpose and field list come first, the return format second. Every clause earns its place.

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?

An output schema exists, so return values need no explanation, and the empty parameter set removes input ambiguity. The only small gap is the absence of any note about device-connection requirements or error behavior, which is minor for a simple read query.

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 tool takes zero parameters, so there is nothing for the description to clarify; baseline 4 applies. The description correctly avoids inventing inputs.

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?

Clear verb+resource with an explicit field enumeration (型号、系统版本、分辨率、序列号) that tells an agent exactly what data comes back. It implicitly separates itself from get_memory_info by scoping to device attributes rather than memory, but it never names a sibling to make the distinction explicit.

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 list of returned fields implies the usage context (use it when you need hardware/OS identity), but there is no statement of when to prefer it over get_memory_info or get_current_activity, and no prerequisites such as requiring a connected device to be selected.

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