record_gameplay

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

With no annotations provided, the description must convey behavioral traits. It states the tool records for a duration and captures selected data, but does not disclose potential side effects (e.g., whether previous recordings are overwritten) or operational constraints. The description is adequate but lacks depth.

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 a single, clear sentence that immediately conveys the tool's purpose and key capabilities. It is front-loaded and contains no extraneous information, making it efficient for an agent to parse.

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's straightforward parameters and lack of an output schema, the description covers the essential functionality. It explains what is recorded and the available options, though it omits details about the recording format or return value, which are not critical for basic usage.

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%, and the parameters (duration, include_input, include_state) are self-explanatory from their names and default values. The description adds minimal extra meaning beyond what the schema already provides, aligning with the baseline score of 3.

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 a specific verb ('record') and resource ('gameplay'), and clarifies what is captured ('input events and/or game state'). This clearly distinguishes it from sibling tools like capture_frames or start_recording.

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?

While the description implies the tool is used to record gameplay, it does not provide explicit guidance on when to use it versus alternatives, nor does it mention exclusions or prerequisites. Sibling tools such as start_recording, stop_recording, and replay_recording are not referenced.

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