trending_history

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, but the description adds genuine behavioral context: it operates offline on previously stored snapshots and defaults to listing the biggest saved trends when unfiltered. It does not state pagination or result-size 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?

The core purpose is front-loaded in the first sentence, and the parameter notes are compact and non-redundant. The layout is slightly fragmented but every line earns its place.

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 values need not be explained, and annotations cover the safety profile; however two of five params are undocumented and there is no explicit alternative-tool routing, leaving minor but real gaps 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?

Schema coverage is 0%, so the description carries the full param burden, yet it documents only 3 of 5 params (contains, geo, days) — with useful detail (whole-word matching, single location code, blank = all, days counted from trend start). limit and min_volume are left completely undefined in both schema and description.

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 specific verb (search) and resource (saved Trending Now history) plus the value dimensions returned (when, how big, how long). It also distinguishes itself from live siblings by naming snapshot_trending as the data source, so an agent can separate it from trending_now/trending_feed.

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?

'Works on what snapshot_trending has stored — no network' and 'with no filter it lists the biggest saved trends' imply usage context, but there is no explicit when-to-use-this-vs-trending_now/trend_details guidance or exclusion criteria.

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