game_window

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

The description indicates both get and set operations are possible, but it fails to disclose behavioral traits beyond what the schema implies. With no annotations (e.g., readOnlyHint), the agent is left uninformed about side effects, such as whether setting fullscreen may disrupt the game state or require specific permissions.

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 short and to the point, consisting of a single phrase. It captures the essential function without extraneous words, making it easy to digest. However, it could benefit from a slightly more structured form (e.g., a sentence) for clarity.

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?

Given the tool has 8 parameters, two possible actions (get/set), and no output schema, the description is insufficient. It does not explain the 'action' parameter, what the get action returns, or how the parameters interact. The agent lacks critical information 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?

Schema description coverage is 100%, so all parameters are documented in the schema. The description merely reiterates parameter names (size, fullscreen, title, position) without adding new semantic context, such as required conditions or interactions between parameters. Baseline 3 is appropriate.

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 'Get/set window size, fullscreen, title, position' clearly states the tool's purpose as getting or setting specific window properties. It distinguishes this tool from siblings like game_set_property or game_get_property by explicitly listing window-related properties.

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 specify when to use this tool versus alternatives like game_set_property for arbitrary properties, nor does it mention prerequisites or scenarios where this tool is preferred.

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