top_videos

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

No annotations provided, so description should disclose behavioral details. It states it returns top videos by views but does not mention sorting order (assumed descending), whether the result is snapshotted or live, performance implications, or if it requires any permissions. The description is vague about the actual 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?

The description is a single sentence of 10 words, extremely concise. It front-loads the core action ('Top videos by views') and provides the date range constraint. Every word is necessary and there is no redundancy.

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?

Given the presence of an output schema (not shown), the description can omit return value details. However, it does not explain what 'top' means (e.g., descending views), how `limit` interacts with pagination, or edge cases (e.g., no videos in range). The description is adequate but leaves some gaps.

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 description coverage is 0%, so the description must add meaning. It clarifies the date format (YYYY-MM-DD) for start and end parameters. However, it does not explain the `limit` parameter beyond its default. The description adds value beyond the schema but is incomplete.

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?

The description clearly identifies the tool as retrieving top videos sorted by views within a date range. The verb 'top' is implicit but understood, and the resource 'videos' is stated. It distinguishes from siblings like `list_videos` (which does not sort by views) and `get_video` (single video). However, it does not explicitly mention that results are limited (default 10).

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?

The description implies usage when you need the most viewed videos in a period. No explicit guidance on when not to use it (e.g., if you need unfiltered list, use `list_videos`). Siblings exist but no alternatives mentioned. The context is clear but lacks exclusions.

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