google_serp_short_videos: GET /

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 explains the scraping behavior (Google Short Videos carousel), parameters (location, country, language, device, pagination), and return fields (title, thumbnail, duration, source, creator, publish date, URL). It does not cover potential rate limits or error states but is transparent about core 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?

Two sentences: first sentence defines the action and key parameters, second sentence lists return fields and use cases. No extraneous text, front-loaded with core purpose.

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 9 parameters (1 required, 4 with enums) and no output schema, the description comprehensively covers the tool's inputs (grouped), outputs (explicitly listed), and intended use cases, making it fully informative for an agent.

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?

With 100% schema description coverage, baseline is 3. The description adds value by grouping parameters (e.g., 'location/uule', 'country (gl/cr)', 'language (hl/lr)') and contextualizing their use beyond the schema. It also describes what the returns contain, aiding parameter understanding.

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 verb 'Get' and resource 'Short Videos Search Results', explicitly mentioning scraping the Google Short Videos carousel for TikTok, YouTube Shorts, Instagram Reels, etc. This distinguishes it from sibling tools targeting other SERP features (images, news, shopping).

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 lists specific use cases (short-form content discovery, viral-trend monitoring, influencer research, etc.), guiding when to use the tool. However, it does not explicitly state when not to use it or mention alternative sibling tools for other content types.

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