game_time_scale

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

The description implies both read and write behavior, but lacks details on side effects (e.g., does setting time_scale affect physics?), permissions, or error conditions. No annotations are provided to mitigate this gap.

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 extremely concise at 6 words, which is efficient but risks being under-informative. It succeeds in being front-loaded with the core action and resource.

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 no annotations or output schema, the description should provide more context about return values, units, default time scale, and what 'timing info' includes. It is insufficient for a tool with two parameters and no additional hints.

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 coverage is 100%, so the schema already documents parameters. The description adds 'Get/set' context but does not provide additional meaning beyond the schema (e.g., allowed values for action, range for timeScale). Baseline of 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 uses specific verbs 'Get/set' and identifies the resource 'Engine.time_scale and timing info', clearly distinguishing it from sibling tools like game_process_mode or game_pause.

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 guidance is provided on when to use this tool versus alternatives, nor on the appropriate context for get vs set operations. The description does not mention prerequisites or exclusions.

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