studio_start

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

No annotations are provided, so the description carries the full burden. It details the behavior: launches a headless browser, captures video, returns config and output directory. It also warns about incorrect background causing flashes and explains the purpose of storage_state_path for credential-free recording.

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 paragraph that efficiently conveys purpose, constraints, and parameter guidance. It is front-loaded with the primary action and then adds details, though it could benefit from slight structural separation.

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 complexity of the tool (8 parameters, nested theme object, no output schema), the description covers all essential aspects: return value, single-session constraint, parameter usage tips, and important caveats. It feels complete for an AI agent.

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%, but the description adds significant meaning beyond the schema. For example, it explains that theme.bg should match the app background to avoid flashes, and that hide_selectors removes UI elements. It provides practical guidance for using storage_state_path and cookies.

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-resource pair: 'Start a recording session'. It clearly distinguishes from siblings like studio_finish and studio_cancel by stating that one session is active at a time.

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?

Explicitly states that only one session can run and must be ended with studio_finish or studio_cancel. Provides context for when to use parameters like theme and hide_selectors, but does not explicitly list when not to use the tool.

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