VidLens

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

No annotations provided, so description carries full burden. Adds valuable timing context [~3-10s] and hints at output format ('compact creator-analysis shape'). However, fails to clarify the 'dryRun' parameter's purpose (suggesting possible side effects not explained) or cache behavior.

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 concise (single sentence + timing), with no wasted words. However, for a 7-parameter tool with zero schema documentation and no annotations, this brevity becomes underspecification rather than efficiency.

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 the tool's complexity. With rich filtering options (shorts/long-form, date ranges, sorting) and no output schema, the description omits parameter semantics, error behaviors, and pagination details needed for correct invocation.

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 has 0% description coverage with 7 parameters. The description fails to compensate by explaining critical parameters like 'dryRun' (unclear why a list operation needs this), 'publishedWithinDays' bounds, or the enum values for 'sortBy'. Names are intuitive but insufficient for proper usage.

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 ('List') and resource ('channel's recent catalog'). The phrase 'compact creator-analysis shape' effectively distinguishes this from siblings like 'inspectChannel' (detailed inspection) or 'buildVideoDossier' (comprehensive reports), though it doesn't explicitly name alternatives.

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?

No guidance on when to use this versus 'inspectChannel', 'findVideos', or 'analyzeVideoSet'. The timing bracket [~3-10s] provides latency expectations but not selection criteria.

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