wavexis_screencast

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

Annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) already indicate safe, read-only behavior. The description adds that results are returned as base64 frames or directory path, which is useful context, but does not disclose potential side effects or requirements like browser session state.

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 short with two sentences and basic Args/Returns structure. It is efficient but could benefit from a more detailed breakdown of parameters and behavior.

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 complexity (multiple parameters, conditional output modes), the description lacks details on how output_dir absence triggers base64 frames, the effect of headless mode, or session requirements. While output schema exists, the description is incomplete for an agent to use optimally.

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 description only mentions 'duration, format, output dir' among many parameters (e.g., url, backend, quality, headless, interval, dimensions, session_id, wait_timeout). With schema description coverage at 0%, the description fails to explain most parameter semantics, leaving the agent to infer from names.

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 'Capture a sequence of screenshots (frame-by-frame)' with a specific verb and resource. It distinguishes from the sibling tool wavexis_screenshot, which captures a single screenshot.

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 usage for capturing frame sequences but provides no explicit guidance on when to use this tool versus wavexis_screenshot or other alternatives. No when-not-to-use or context is given.

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