youtube_analytics_top_shorts

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

No annotations are provided, so the description carries the full burden. It states it returns per-Short metrics sorted by view count, but doesn't disclose whether this is read-only, what specific metrics are included, whether shorts-only content is considered, or any rate-limit/auth requirements. The behavior is partially disclosed but lacks depth for a data-retrieval tool.

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 compact and front-loaded with the core purpose in the first sentence. The parameter documentation is efficient. Minor waste: 'sorted by view count' is somewhat redundant given 'top-performing by views' but adds precision about ordering.

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?

For a simple analytics tool with 3 optional parameters and no output schema, the description covers the main inputs and output concept. However, it doesn't specify what metrics are returned (only views are mentioned), whether averages or totals are provided, and doesn't clarify behavior when no Shorts exist in the date range. These gaps matter for an analytics 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 description coverage is 0%, so the description must document all 3 parameters. It does describe start_date (format YYYY-MM-DD, default 28 days ago), end_date (format, default today), and max_results (max 200). This adds format and default context beyond the bare schema. However, it doesn't clarify date semantics (inclusive/exclusive) or what happens when max_results exceeds 200.

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 'Get top-performing Shorts by views' with a specific verb (get), resource (Shorts), and metric (views). It distinguishes itself from siblings like youtube_analytics_top_videos by specifying 'Shorts' as the resource type.

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 context through the 'top-performing Shorts by views' framing and describes what it returns. However, it doesn't explicitly state when to choose this over youtube_analytics_top_videos or youtube_analytics_overview, nor does it mention any exclusions or alternatives.

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