VidLens

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

Includes valuable timing estimate '[~5-20s, ~2s per video]' not found in annotations. Mentions 'local' storage implying disk side effects. However, lacks disclosure on idempotency, error handling (partial failures), or what happens when reindexing existing videos despite the 'reindexExisting' parameter.

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 structure: single declarative sentence followed by concise timing metadata in brackets. No filler words or redundant phrases. Information density is high relative to length.

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?

Inadequate for a complex 13-parameter configuration tool. Missing explanation of chunking strategies, embedding provider differences, collection lifecycle (create vs update), and dry-run behavior. Without output schema or annotations, the description should elaborate on these operational dimensions.

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 across 13 parameters, the description fails to compensate for the undocumented schema. Only implies the required 'videoIdsOrUrls' parameter ('one or more videos'). Critical configuration options (chunkStrategy, embeddingProvider, dryRun, activateCollection) receive no explanation despite being complex enums and booleans.

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?

States specific action (import videos), destination (local transcript collection), and purpose (semantic search). Distinguishes from sibling tools like 'readTranscript' or 'importComments' by emphasizing the persistent collection aspect, though could explicitly contrast with transient transcript retrieval.

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?

Provides no guidance on when to use versus alternatives like 'importPlaylist' (for bulk playlist imports) or 'readTranscript' (for one-off transcript access). No mention of prerequisites like existing collections or video accessibility requirements.

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