clear_game_info

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

With no annotations provided, the description carries the full burden of disclosing that this is a destructive operation. While 'Clear all' signals destructiveness, it doesn't explain reversibility, what exactly counts as 'game project information,' or what happens to existing data after the operation.

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 a single, front-loaded sentence with no wasted words. 'Clear all game project information and start fresh' delivers the core message efficiently.

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?

The tool is simple (one boolean parameter, full schema coverage), but as a destructive mutation with no annotations and no output schema, the description leaves gaps about consequences and post-deletion state. It doesn't mention whether cleared data can be recovered or when the agent should use this reset operation.

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%, with the confirm parameter already documented as 'Must be set to true to confirm deletion.' The description adds no additional parameter semantics beyond the schema's existing coverage, so the baseline of 3 applies.

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 a specific verb ('Clear') with a clear resource ('all game project information'), making the purpose unambiguous. It naturally distinguishes itself from sibling tools like get_game_info and update_game_info by signaling a full reset rather than retrieval or modification.

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 phrase 'and start fresh' implies the tool is for resetting the project state, but the description provides no explicit guidance on when to choose this over alternatives like update_game_info or delete_actor_template. It also doesn't state prerequisites or exclusions (e.g., that the operation must be confirmed).

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