record_and_export

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

With no annotations, the description carries the full burden. It explains the core flow (open, wait, stop, export) and auto-configuration based on platform. Missing details include whether recording starts immediately after opening the URL and what 'wait' entails precisely.

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 very concise: a two-sentence summary followed by bullet examples. Every sentence is essential, front-loaded, and easy to scan.

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 (8 parameters, platform presets, auto-configuration), the description covers the workflow and parameter relationships well. It lacks details about return values or side effects (no output schema), but still delivers a solid understanding.

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%, baseline 3. The description adds value by explaining how platform values map to dimensions and format, and clarifies that gifFps/gifWidth apply only to GIF output, going beyond the schema descriptions.

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 the tool as an all-in-one solution that opens a URL, waits, stops recording, and auto-exports. It provides specific platform examples (GitHub, Reels, TikTok, YouTube) and contrasts with sibling tools like record_page and smart_export.

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 explicitly guides when to use the tool (for combined recording and export with platform presets) and offers an alternative path via custom parameters. However, it does not explicitly name sibling tools for scenarios like separate record/export steps.

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