Detect Scenes

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

With no annotations, the description carries the full burden. It mentions the detection method and output format, but lacks details on side effects, prerequisites (ffmpeg), error handling, or behavior with edge cases like invalid paths. Adequate but not thorough.

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 consists of two concise sentences. It front-loads the core purpose and method, followed by output and use case. 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 the complexity (4 parameters, no output schema, no annotations), the description is incomplete. It omits parameter explanations, return format, error scenarios, and prerequisites. The essential behavior is conveyed, but significant gaps remain for effective agent use.

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 only 25% (only 'threshold' has schema description). The tool description adds zero parameter information beyond the schema. For a low-coverage tool, this is insufficient; it fails to clarify unclear parameters like 'start_time' or 'end_time'.

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 it detects scene cuts using ffmpeg and returns timestamps with confidence. It also notes it's ideal for decoupage (1 frame per shot). However, it does not explicitly differentiate from sibling tool 'decupar', which may have similar functionality.

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 clear usage context by stating it's ideal for decoupage, implying a specific use case. However, it does not give explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives among siblings.

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