google_trends_explore_related_topics

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

The description notes that an empty array is returned when Google returns no topic rows, which is helpful. However, it does not disclose other behavioral traits (e.g., idempotency, latency, authentication requirements) in the absence of annotations.

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 concise (two sentences) and front-loaded with the primary purpose. No redundant information, though it could benefit from more structured parameter details.

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 nested input object with no schema definition, the description should provide more context on the request structure. The mention of 'term/filter combination' is insufficient for an agent to construct a valid input. No output schema is present, so the description should compensate but does not.

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's 'request' parameter description is generic ('Explore request'), and the tool description adds only a hint about 'term/filter combination' without specifying the object's structure. With 100% schema coverage but minimal descriptions, the description adds limited semantic value.

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 it returns the 'related topics widget' from the Google Trends Explore widget flow, which differentiates it from sibling tools like interest over time or top queries. It also mentions handling empty results, reinforcing the purpose.

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?

No guidance on when to use this tool versus alternatives (e.g., other google_trends_explore_* tools). No prerequisites, exclusions, or typical use cases are mentioned.

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