Trending now

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

No annotations are provided, so the description and parameter descriptions carry the full burden. They disclose that 'rpc' returns ~50 items with growth percentages, 'rss' returns 10 with news articles, and 'auto' falls back, but do not describe sorting order or potential failure modes.

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 succinct yet information-dense, using two well-structured sentences with a clear em-dash aside. Every clause adds functional value, avoiding redundancy or filler.

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?

With no output schema, the description reasonably communicates what each backend returns (items, growth percentages, news articles). It does not specify exact response shape, but that is not essential for this simple list tool given the parameter descriptions.

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?

All three parameters have descriptions with explicit meaning and constraints. 'limit' has min/max, 'region' explains empty string as worldwide and accepts ISO codes, and 'backend' details the behavior of each enum value, going beyond basic schema info.

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 tool lists trending searches in a country, using specific verbs like 'List' and 'surging'. It also distinguishes its discovery purpose from user-named term queries, and explains the 'rss' backend's role in providing explanatory news articles.

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 states when to use the tool: for discovery, news, monitoring, and real-time questions. It also provides specific guidance on choosing the 'rss' backend when the user wants to know why something is trending, and contrasts with default behavior.

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