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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds useful behavioral context beyond annotations: that search traffic and related news are returned only 'when available', warning the agent that some rows will be sparse. It omits rate-limit and pagination behavior, but that is a minor gap against the annotation coverage.

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?

Two sentences, zero waste, with the description of the returned data front-loaded ahead of the disambiguation sentence. Nothing to trim.

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 an output schema and a fully documented parameter set, the description needs little else; it adds the detail-tool routing and the availability caveat. Complete enough to call correctly, though a note on the category/window defaults could have helped.

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 description coverage is 100% with all nine parameters (locale, tz, geo, limit, status, window, sort_by, category, time_range) documented inline, so the baseline is 3. The description only gestures at the geo filter ('for a region') and adds no format or interplay details beyond the schema.

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 (Fetch) and resource (Google Trends Trending Now topic rows) with scope ('for a region') and names the exact sibling it is not. An agent can distinguish it from google_trends_trending_detail without opening either schema.

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 routes the drill-down case to google_trends_trending_detail ('for one topic's details'), which is the key sibling decision. It does not state when *not* to use this tool or mention the explore/* family, but the primary selection condition is covered.

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