google_trends_explorer

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

With no annotations, the description carries full disclosure burden. It states the core capability but lacks details on output format, limitations beyond keyword count, potential rate limits, or whether it is a read-only operation. It does not contradict any annotation, but leaves significant behavioral characteristics undisclosed.

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 a single, concise sentence that front-loads the main action and constraint. It contains no filler or redundancy. While it could add a bit more information without bloating, it is appropriately sized for its purpose.

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?

For a tool with 4 parameters, no annotations, and absent schema descriptions, the description is insufficient. It does not explain how 'timeframe,' 'geo,' or 'format' affect results, nor does it clarify the output structure despite having an output schema. An agent would struggle to set parameters correctly beyond 'keywords.'

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% (no property descriptions). The description mentions only 'keywords' and its limit ('up to 5'), but does not explain 'geo,' 'format,' or 'timeframe' semantics. Even the keyword meaning is only partially covered (limit, not usage examples or expected format). Thus, it adds minimal value beyond property names.

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 states a specific verb ('explore') with a clear resource ('Google Trends') and includes key details: 'interest over time and related queries' and 'up to 5 keywords.' This distinguishes it from sibling research tools like gads_keyword_ideas or gsc_search_queries, which target different data sources.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or competing tools. An agent must infer usage context from the name and domain alone.

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