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

With no annotations, the description carries the full burden. It discloses the billing cost (1 credit per call) but provides no insight into the response format, authentication needs, rate limits, or any other behavioral aspects. The word 'Explore' is not informative.

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 extremely concise, with no fluff or unnecessary words. The billing information is useful, and the structure is clean, though it could have included more substantive content without harming conciseness.

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?

Even for a simple tool with no parameters, the description is incomplete. It does not state what the tool returns (e.g., list of trending videos, trending searches, etc.) or how it differs from the many v1 tools. The billing info and vague 'Explore' are insufficient.

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?

The tool has zero parameters, so the schema is fully covered (100%) and there is nothing to explain. The baseline for 0 parameters is 4, and the description doesn't need to add parameter details.

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 says 'Trending Group: Explore', which implies the tool is for exploring trending content but lacks a specific verb-resource statement. The name 'get_v2_trending' and title 'Trending' hint at the purpose, but the description itself is vague about what exactly is retrieved.

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?

No guidance is provided on when to use this tool versus the many sibling tools. The phrase 'Trending Group' suggests it is for trending content, but there are no explicit exclusions or alternatives mentioned.

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