game_os_info

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

The description states a read operation ('Get'), but with no annotations, it lacks explicit behavioral traits. For a simple info-retrieval tool, it is adequately transparent, though no further details (e.g., side effects, permissions) are given.

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 superfluous words. It is concise and front-loaded with the action and resource types.

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 description lists the information categories but omits the return format or structure. Since there is no output schema, more detail would help an agent understand what to expect, but for a simple getter, it meets minimum requirements.

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 has no parameters, so the schema covers all inputs. The description does not need to add parameter details. Baseline 4 is appropriate as no additional semantics are required.

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 specifies the tool's purpose: retrieving platform, locale, screen, adapter, and memory info. It uses a specific verb ('Get') and lists the resources, distinguishing it from siblings like 'game_locale' which focus on a single aspect.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives such as 'game_locale' or 'game_performance', nor does it mention any prerequisites or context.

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