youtube_analytics_top_shorts

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

With no annotations, the description carries the full burden of behavioral disclosure. It discloses that the tool returns per-Short metrics sorted by view count and provides default date range details. However, it does not mention authentication requirements, rate limits, or specify which metrics are included beyond views, leaving gaps in transparency.

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 succinct and well-structured: a one-sentence purpose, a one-sentence return summary, and an Args list with clear definitions. Every sentence provides value; there is no fluff or unnecessary repetition.

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?

The description covers the basics but lacks details that are important given no output schema or annotations. It does not list the specific metrics returned (only 'per-Short metrics'), nor does it mention authentication prerequisites or any channel-specific requirements. This leaves uncertainty for an agent deciding whether to use the tool.

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%, so the description must add meaning to parameters. It does so effectively by explaining each parameter: start_date and end_date with format (YYYY-MM-DD) and defaults, and max_results with a max limit of 200. This goes beyond the bare schema and compensates well.

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 states the tool's function with a specific verb and resource: 'Get top-performing Shorts by views.' This distinguishes it from sibling tools like top_videos or other analytics tools. The additional line about returning per-Short metrics sorted by view count reinforces the purpose.

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?

Usage context is implied by the tool's name and purpose (for retrieving top Shorts), but there is no explicit guidance about when to use this tool versus alternatives like top_videos. No prerequisites, exclusions, or alternative recommendations are provided.

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