Catalog B-rolls

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

No annotations provided, so the description must carry the burden. It explains the tool reads and analyzes clips (non-destructive) and returns a catalog, but does not mention auth needs, rate limits, or any side effects. Adequate but not fully transparent.

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?

Two sentences that front-load the core functionality and provide a usage hint. Every word earns its place with zero redundancy.

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?

With 4 parameters and no output schema, the description should explain the return structure and parameter effects. It only mentions 'catálogo completo com frames representativos' without details on format or how threshold/resolution affect output. Incomplete for moderate complexity.

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 50% (video_paths and max_shots_per_clip have descriptions). The description adds no parameter-specific information beyond the schema defaults for threshold and resolution, failing to compensate for the coverage gap.

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 visually analyzes a list of b-roll clips, performs decoupage (shot detection/segmentation), and returns a catalog with representative frames. It also suggests usage before match_edit, distinguishing it from siblings like decupar or detect_scenes.

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?

Explicitly says 'Use antes de match_edit' to allow Claude to see available visual content. Does not mention when not to use or alternatives, but provides clear context for a specific workflow step.

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