video_ai_scene_detect

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

The description does not disclose any behavioral traits beyond the verb 'detect'. It omits whether the tool modifies the video, returns scene timestamps, or requires specific input formats. With no annotations, the burden is unmet.

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 single sentence is concise but sacrifices necessary detail. It front-loads the action but omits critical information about input, output, and parameters. A description this brief fails to serve its purpose effectively.

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 existence of a sibling tool and an output schema, the description is severely incomplete. It does not address how the tool differs, what the output contains, or how parameters influence behavior. The context signals demand a richer description.

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?

With 0% schema description coverage, the description must explain parameter meanings. It does not define 'input_path', 'threshold', or 'use_ai', adding no value beyond the parameter names. Essential context for correct invocation is missing.

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 states the core action ('detect scene changes'), but fails to differentiate from the sibling tool 'video_detect_scenes'. Without context on what makes this AI-based version distinct, the purpose is clear but not uniquely identifiable among alternatives.

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?

No guidance on when to use this tool instead of the similarly named 'video_detect_scenes' or any other video analysis tools. The description lacks prerequisites, typical use cases, or exclusions, leaving the agent without decision support.

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