Analyze recording for black/dim frames

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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds context: it explains the heuristic nature of bucket ranges, the need for calibration, and that full timeline is omitted unless includeFullTimeline=true. This goes beyond annotations.

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?

Three sentences, front-loaded with purpose. Every sentence adds value: first defines core function, second adds calibration note, third mentions mode and timeline option. No wasted words.

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 11 parameters and an output schema (present but not shown), the description covers the main purpose, calibration, mode usage, and timeline behavior. It would be stronger if it explained the output format, but the output schema exists. Almost complete for a complex tool.

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 27% (3 of 11 params). The description adds meaning for mode (flash sets defaults) and mentions exportSampleFrames and includeFullTimeline, but leaves many parameters (fps, path, marks, etc.) unexplained. The description compensates partially but not fully for low schema coverage.

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 samples mean grayscale over an MP4, detects black/dim runs, and classifies brightness buckets. It uses specific verbs and distinguishes from siblings like mobile_theme_flash_report by mentioning mode='flash' for regressions.

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 provides explicit guidance for using mode='flash' and calibrating with exportSampleFrames. It implies the tool is for analyzing recordings for brightness issues, which is clear but does not explicitly state when not to use it.

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