record_video

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

Annotations already signal a non-read-only, open-world operation, but the description adds no behavioral context beyond the literal action. It does not disclose that recording is an ongoing process requiring a separate stop call, nor does it mention output-file behavior or other side effects. There is no annotation contradiction, but the description fails to add meaningful transparency.

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, front-loaded sentence with no filler or redundant detail. It states the action, resource, and implementation method efficiently.

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?

Despite the rich schema, the description omits critical operational context such as how long recording lasts, how to stop it, and what the tool returns. The existence of a stop_recording sibling makes this gap especially significant, as the agent cannot infer the full workflow from the description alone.

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?

The input schema provides 100% description coverage with detailed explanations for all six parameters, including udid, codec, display, and output_path. The description itself adds no parameter-level semantics, so the baseline score of 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 uses the specific verb 'Records' and identifies the resource as 'a video of the iOS Simulator'. It clearly distinguishes the tool from sibling tools like screenshot (still image) and stop_recording (ending a 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?

The description implies the tool is used when a video of the simulator is needed, but it provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives or prerequisites such as a booted simulator or how this relates to screenshot or stop_recording.

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