list_game_videos

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

With no annotations provided, the description carries the full disclosure burden. It adds valuable behavioral context about the split-screen layout (content top, game bottom) and hints at output structure (gameVideoName field), but omits pagination behavior details, rate limits, or response format specifics expected for a read operation with no safety annotations.

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?

Two sentences with zero waste. First sentence front-loads purpose and specific domain context; second sentence provides actionable usage guidance. Every word earns its place.

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 simple 2-parameter list tool with no output schema, the description adequately compensates by revealing the key output field (gameVideoName) and the specific domain (split-screen overlays). Slight gap on pagination return structure (total counts, hasMore flags), but sufficient for tool selection.

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 description coverage is 100% (page number and items per page are clearly documented), so the baseline expectation is met. The description does not add parameter-specific semantics, but none are needed given the comprehensive schema documentation.

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 uses specific verb 'List' with clear resource 'gameplay videos' and distinguishes from siblings by specifying the unique use case 'for split-screen overlays (content top, game bottom)', clearly differentiating it from list_music, list_templates, and other list tools.

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 explicit guidance on when/how to use the output ('Use the exact gameVideoName when creating shorts'), referencing the sibling tool create_short. However, it lacks explicit 'when not to use' guidance or contrast with alternative tools like list_templates.

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