get_game_state

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

The verb 'get' implies read-only, but no explicit statement about safety or side effects. Without annotations, the description should be more explicit about behavioral traits.

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 concise (two sentences plus a bullet list), front-loads the purpose, and adds key fields without unnecessary detail.

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 complexity of the game state and that an output schema exists, the description's enumeration of key fields is sufficient. It could list all sections more comprehensively, but for decision-making it covers the essentials.

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?

No parameters exist, so the description adds value by explaining the output structure and key fields beyond the schema which only specifies no parameters.

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 states the tool retrieves the full game state, lists the returned sections, and distinguishes from sibling tools that get specific layers or items.

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 description implies use for decision-making by highlighting key fields, but does not explicitly state when to use this tool versus alternatives like get_state_layer or get_game_data_item.

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