Video Info

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

Without annotations, the description fully carries the behavioral burden. It explicitly states the tool reads metadata without processing frames, implying read-only and non-destructive behavior. It could add more details (e.g., file existence checks) but is sufficient for a simple metadata reader.

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 efficiently deliver the purpose and usage context without any extraneous information. Every sentence is valuable.

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?

For a simple metadata-reading tool with one parameter and no output schema, the description is complete. It lists the metadata fields and positions the tool relative to its siblings, providing all necessary context.

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?

There is only one parameter with schema description coverage at 100%. The description does not add extra meaning beyond the schema's 'Caminho absoluto do arquivo de vídeo.' Baseline score is appropriate.

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 specifies the action (lê metadata) and the resource (vídeo), listing specific metadata fields (duração, fps, resolução, codec, tamanho) and distinguishing itself as a cheap initial step before frame extraction or scene detection.

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 states 'Passo inicial barato antes de extrair frames ou detectar cenas,' clearly indicating when to use the tool as a preliminary step. It does not explicitly exclude other contexts, but the context is well implied.

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