game_resource

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

No annotations beyond title. Description lacks behavioral details such as side effects of save (overwrite?), required permissions, or error states. The preload mention contradicts schema.

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?

Extremely short (3 words), but lacks necessary detail, especially given the schema-action mismatch. Conciseness sacrifices clarity.

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?

Missing output schema and descriptions of return values or effects. As a mutation-capable tool (save action), more context is needed about what changes are made and side effects.

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 covers all parameters with descriptions (100%). Description adds no new info beyond the schema; the preload reference is misleading. Adequate but not improved.

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 states 'Runtime resource load, save, or preload' but the input schema's action parameter only lists 'load, save, exists', not 'preload'. This mismatch causes confusion about the tool's actual capabilities.

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?

No guidance on when to use this tool versus siblings like game_get_property, game_set_property, or manage_resource. Missing context for agent decision-making.

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