game_tween_property

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

With no annotations, the description should explain key behaviors (e.g., whether the tween blocks, returns a reference, or requires cleanup). It only states 'tween a node property' without disclosing if the tool modifies the property immediately or over time, or what side effects occur.

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 very concise, consisting of a single sentence. However, it is too brief and lacks structure, missing key information that would benefit from additional context.

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?

Given the tool has 6 parameters, no output schema, and no annotations, the description fails to provide sufficient context for an agent to use it correctly. It does not cover behavior, return values, or usage scenarios.

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 coverage is 100% and each parameter has a clear description. The tool description adds no extra meaning beyond the schema. Baseline 3 is appropriate.

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 clearly states the verb 'tween' and the resource 'node property', making it unambiguous that this tool animates a property over time. It distinguishes from immediate property-setting tools like game_set_property.

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 is provided on when to use this tween tool versus alternatives such as game_set_property (for immediate changes) or game_play_animation (for complex animations). The description does not mention prerequisites or context.

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