game_video

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

The description mentions basic actions but omits 'create' and 'get_status' which are present in the schema. With minimal annotations, the description should cover all actions; it does not fully disclose the tool's scope.

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 short and efficient, but it omits part of the action set. It earns its place but could be more representative without adding length.

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?

With 9 parameters and no output schema, the description should provide more context about action behavior and parameter relationships. It only covers 3 of 6 actions, leaving significant gaps for a complex tool.

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%, so parameters are well-described in schema. The description adds no extra meaning beyond listing a few actions, so baseline 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 clearly states 'Video playback control' with specific verbs: play, pause, stop, seek, and targets 'VideoStreamPlayer'. This distinguishes it from sibling tools like game_audio_play or game_animation_control.

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 description implies usage for video playback control but does not explicitly state when to use this tool versus alternatives, nor any prerequisites or exclusions. The context is clear but lacks guidance.

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