new_game

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

Discloses behavioral traits: player_class affects town reception, unknown classes passed verbatim, skip_intro starts at loop 2 with recap. Lacks mention that it resets current progress, but still informative.

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?

Concise, front-loaded with purpose. Every sentence adds value without verbosity. Could be slightly more structured but efficient.

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?

Covers purpose, parameter behavior, and special cases adequately. Missing explanation of return value and explicit reset indication, but sufficient for a start tool.

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 has 0% description coverage, but description adds semantics for player_class (list and fallback) and skip_intro (effect). Name parameter remains unexplained, but overall adds significant value beyond schema.

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?

Clearly states 'Start a fresh save' with specific verb and resource. Lists valid player_class options and explains behavior for unknown classes. Uniquely distinguishes from sibling tools as the only game-starter.

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?

Provides explicit context for using the tool to start a new game and clarifies usage of skip_intro for replays. No explicit when-not alternatives needed due to uniqueness.

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