selectRestart

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

No annotations provided, so description must fully disclose behavior. It mentions retrieving a summary and instructing to create a new game but does not clarify side effects, authorization needs, or rate limits. The mixed read/instruction nature is ambiguous.

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?

Two sentences with front-loaded main action. Efficient and easy to parse, though could benefit from slightly more structure (e.g., separating output and side effects).

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 output schema and no annotations, the description is adequate for a simple tool but lacks details on what the 'final game state summary' contains and how the instruction to create a new game is executed. Sibling tools (createGame) hint at the workflow, but more clarity would help.

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% for the single parameter gameId, so baseline is 3. The description adds no additional meaning beyond the schema's 'ID of the ended game'.

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?

Description clearly states the tool restarts the game after game over and retrieves a final game state summary. It distinguishes itself from siblings like createGame by not actually creating a new game but instructing to do so. However, the exact scope of 'instructs' is slightly ambiguous.

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?

Explicitly specifies when to use ('when the player clicks the Restart button on the Game Over screen'). No mention of when not to use or alternatives, but the context is clear.

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