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

With no annotations provided, the description carries the transparency burden. It explains the output shape (scored queries and growth) but does not mention potential errors, rate limits, or behavior when a keyword has no related queries. It is honest about what is returned, but omits edge-case 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 description is verbose and contains redundant information. The timeframe allowed values are listed twice: once as prose describing daily vs. weekly series, and again as a parenthetical pipe-separated enum. This repetition adds length without adding clarity, though the core content is well-organized.

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?

Given the lack of an output schema, the description adequately explains the result format (top queries relative scores, rising queries with growth) and provides all needed input conventions. It lacks explicit error-handling information, but otherwise gives a complete picture for an agent to make and interpret a call.

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 input schema is generic (a single free-form params object) and provides no property definitions, so the description fully compensates. It explains that 'keyword' is the search term, 'geo' is an ISO-3166 alpha-2 country code, and 'timeframe' is one of an explicit enum list, including an example illustrating usage.

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 returns Google Trends related queries for a keyword, describing both top queries (scored 0-100) and rising queries (with percentage growth), and positions it for SEO keyword research, content planning, and spotting breakout demand. This distinguishes it from similar sibling tools like related_topics and interest_by_region.

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 description includes concrete usage guidance: an example parameter set for 'bitcoin' in the US, a full allowed timeframe list, and geo format specification. It states the primary use cases but does not explicitly contrast with sibling tools like related_topics or interest_by_region, which would have made the when-to-use guidance stronger.

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