Trends.Trending Now

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about data freshness/refresh cadence, result limits, rate limits, or whether a country with no signal returns empty versus an error. Only the word 'Currently' implies recency.

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?

One short, front-loaded sentence with no filler. It is efficient, though the terseness borders on under-specification rather than deliberate brevity.

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?

An output schema exists, so return-shape explanation is not required, but for a discovery/trends tool with no annotations the description should at least cover freshness and geographic granularity. Neither is present, leaving the agent to guess how results differ from the three sibling trends tools.

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 single geo parameter has 0% schema description coverage. The description only implies it is a country, adding no format guidance (ISO-3166 alpha-2 vs country name) beyond the schema's 'US' default. That is a thin compensation for a completely undocumented parameter.

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?

States a concrete resource (trending searches) scoped to a country, which is more specific than the bare tool name. It does not, however, distinguish itself from siblings like trends.related_queries or trends.interest_over_time, so the agent must infer the boundary from the name alone.

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 parenthetical '(breakout demand)' hints at an analytical use case but gives no explicit when-to-use rule and names no alternative. Nothing tells the agent why to pick this over related_queries or interest_by_region.

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