analyze_short

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds behavioral context by specifying the analysis extracts hook timing, CTA patterns, etc., and notes the video must be a Short. No contradictions.

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?

Two sentences plus a bullet point. Front-loaded with 'SHORTS-SPECIFIC TOOL'. Every sentence adds value, 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?

For a single-parameter tool, the description provides purpose, usage, and output details. Lacks explicit mention of return format but the listed extraction items give sufficient context. Could be improved with a brief note on response structure.

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 100% with a single parameter videoId. Description adds value by clarifying that the video ID must be for a Short, which is not explicit in the schema description. However, it doesn't elaborate on format or validation rules.

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?

Clearly states it's for YouTube Shorts (<60 sec) and lists specific analysis outputs (hook timing, CTA patterns, words-per-second, hashtags, visual frame). Differentiates from sibling deep_analyze_video by instructing to use this instead for Shorts.

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?

Explicitly says 'Use this instead of deep_analyze_video for Shorts' and provides a complementary tool (get_shorts) for discovery. Provides clear when-to-use and when-not-to-use guidance.

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