VidLens

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

No annotations provided, so description carries full burden. Adds valuable latency hint [~1-3s] and mentions 'long-video safeguards' implying chunked processing. However, missing: return format structure, authentication requirements, rate limits, and error handling for videos without transcripts.

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 dense single sentence packs mode options, behavioral safeguards, and latency estimate. Every word earns its place. Front-loaded with primary action. No redundant or filler text.

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 8 parameters, 0% schema coverage, no output schema, and no annotations, the tool complexity exceeds the description's coverage. Critical gaps remain in parameter semantics and return structure for a multi-modal read operation.

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 coverage is 0%, requiring heavy description compensation. Mentions modes (mapping to 'mode' enum) and implies pagination/chunking, but leaves 5+ parameters undocumented: dryRun purpose, language code format, includeTimestamps effect, and videoIdOrUrl format expectations.

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?

Specific verb 'Read' + resource 'transcript' with clear mode differentiation (summary, key moments, chapters, full). Distinguishes from sibling searchTranscripts by emphasizing consumption modes vs. search. Could be 5 if it explicitly contrasted with searchTranscripts or inspectVideo.

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?

Lists available modes but provides no guidance on when to use each (e.g., when to choose summary vs. key_moments). Fails to mention when to use vs. sibling searchTranscripts or inspectVideo. No prerequisites or error conditions mentioned.

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