game_resource

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

No behavioral details beyond the basic actions. Absence of annotations places full burden on description, yet it fails to disclose side effects (e.g., file overwrites on save), permissions, or runtime implications.

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 concise but slightly misleading by mentioning 'preload' not in the action list. Could be improved by aligning with schema or including structured steps.

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?

Incomplete given 4 parameters and no output schema. Lacks explanation of return values, error handling, or distinctions between 'load', 'save', and 'exists'. Many sibling tools exist, so more detail is needed.

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. The description adds no extra semantic value, such as clarifying how 'path', 'nodePath', and 'property' interact. Baseline 3 is appropriate given high schema coverage.

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 states 'load, save, or preload' resources, which clearly identifies the tool's purpose. However, the input schema only lists 'load', 'save', and 'exists' as actions, omitting 'preload', causing slight inconsistency.

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 'create_resource' or 'load_sprite'. No mention of alternatives or context-specific usage.

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