VidLens

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

Adds valuable behavioral context not in annotations: '[~3-10s]' indicates latency cost, and 'one-shot' suggests atomic execution. However, missing critical safety disclosure since annotations are absent—doesn't clarify if 'Build' creates persistent storage, requires auth, or is idempotent.

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?

Extremely efficient single-sentence structure with high information density. The timing annotation '[~3-10s]' is appended without clutter. No filler words or tautology.

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?

Adequate for basic comprehension given the tool's complexity (6 params, rich functionality), but gaps remain: no output schema means the description should ideally sketch the dossier structure/return format, and 0% schema coverage leaves half the parameters unexplained.

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 partially compensates by mapping boolean flags to conceptual groups ('core metadata/transcript readiness' vs 'extended with comments, sentiment'). However, it fails to explain 'commentSampleSize', 'dryRun', or input format expectations for 'videoIdOrUrl'.

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?

Clear verb ('Build') and resource ('video dossier') with specific scope ('one-shot'). However, it doesn't explicitly differentiate from siblings like 'inspectVideo' or 'analyzeVideoSet' which appear to overlap in 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?

Implies usage patterns through 'optionally extended with comments, sentiment, and provenance' suggesting when to toggle flags, but provides no explicit guidance on when to choose this tool over alternatives like 'inspectVideo' or when to avoid it.

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