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

Annotations already declare readOnly, idempotent, non-destructive, and non-open-world behavior. The description adds valuable return-content detail beyond the annotations by listing proposal, approval status, revision, project files, compiled HTML, version, and asset:// references.

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 front-loaded with the read action and its returned components, and it avoids unnecessary filler. The final preservation instruction is brief, though somewhat less essential for a read-only tool.

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?

For a two-parameter read tool with no output schema, the description usefully enumerates the returned content and notes 'Read before editing.' However, it leaves the required workspaceId/gameId semantics unexplained, which is a meaningful gap given 0% schema description coverage.

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 schema has 0% description coverage for workspaceId and gameId, yet the description does not explain either parameter's format, pattern, or role. It only implies that a game is identified, leaving the required workspace scoping undocumented in both description and 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?

States a specific verb and resource: 'Read a game' and enumerates the game's proposal, approval status and revision, project files, compiled HTML, current version, and asset references. The singular, ID-based read is distinguishable from list_experience_games and save_experience_game, but no sibling is named explicitly.

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 clear context with 'Read before editing,' which tells the agent when this tool is appropriate. It does not name alternatives or state when not to use it, so it falls short of explicit routing guidance.

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