Game state

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

readOnlyHint=true already tells the agent this is a safe read, lowering the bar. The description adds useful content detail by enumerating the payload (scene, tick, time, renderer, frame stats, inspect data), but says nothing about cost, snapshot freshness, or how it relates to the sibling frame/profile tools.

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?

A single compact sentence-fragment with no filler; every item named is meaningful payload. It loses a point only because the fragment lacks a leading verb that would frame the whole list.

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?

With no output schema, the description carries the burden of describing return content, and its enumeration partially does that. However, with seven or more closely related game_* inspection siblings and no routing hints, an agent lacks enough context to know when this is the right call versus game_frames or game_profile.

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 per the rubric the baseline is 4. There is no parameter behavior the description needs to compensate for.

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 is a bare noun list ('Current scene, tick, time, renderer, frame stats...') with no verb or framing sentence, so the purpose is only implied rather than stated. It does let an agent infer this is a read of live game state rather than a capture or profile, but it never explicitly distinguishes itself from overlapping siblings like game_frames or game_profile.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the many game_* siblings (game_frames, game_profile, game_capture, game_notes). The agent must guess which sibling returns which slice of state.

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