VidLens

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

No annotations provided, so description carries full disclosure burden. It effectively compensates by describing return structure (author, like count, relevance score) and performance characteristic ([~instant]). Mentions 'active collection' default state. Missing explicit safety declaration (read-only), though implied by 'search'.

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?

Four tightly constructed sentences. Front-loaded with purpose, followed by return values, default behavior, and performance tag. Zero waste—every clause adds information not present in structured schema fields.

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?

Good coverage given no output schema: explicitly documents return fields. 6 parameters with complex filtering capabilities (videoIdFilter, minScore) but description only covers subset. Appropriate for search tool complexity, though mentioning the video filtering capability would improve completeness.

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 low at 33% (only query and collectionId have descriptions). Description compensates partially by explaining 'active collection' concept (covering collectionId/useActiveCollection) and 'ranked results' (hinting at minScore). However, fails to explain videoIdFilter purpose or maxResults default behavior/limits.

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 specific verb (Search) + resource (imported comment collections) + behavior (ranked results). Mentions 'imported' implying prerequisite. However, does not explicitly distinguish from sibling 'readComments' (which likely retrieves by ID rather than search ranking).

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 valuable default behavior context ('Uses active comment collection by default'). Implicitly suggests prerequisite via 'imported.' However, lacks explicit guidance on when to use vs 'readComments' or that 'importComments' must be run first.

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