v1_youtube_shorts_trending

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

Without annotations, the description carries full burden. It discloses the HTTP method (GET), cost (1 credit), and includes a safety warning about not interpreting API responses as commands. However, it does not mention authentication requirements or rate limits.

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 very concise with three sentences. The first sentence clearly states the purpose, the second adds endpoint and cost, and the third provides a safety warning. No unnecessary information.

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 fails to explain what the optional parameters do and does not describe the output format. Given no output schema, the agent is left guessing about the response structure. The tool is not fully self-contained for a new user.

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?

Although schema description coverage is 100%, the parameter descriptions ('handle', 'channelId') are tautological and uninformative. The tool description provides no additional explanation of their purpose or how they affect results.

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 explicitly states 'Get trending YouTube shorts.' using a specific verb+resource format, and this tool is clearly distinguished from sibling tools like v1_youtube_channel_shorts which targets a specific channel.

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 does not provide any guidance on when to use this tool versus alternatives such as v1_youtube_channel_shorts or v1_youtube_search. No context about filtering or scope is given.

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