google_trends_explore

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

No annotations exist, so the description must disclose behavioral traits. It only states the tool 'returns normalized Google Trends keyword analytics' without mentioning rate limits, authentication requirements, or the fact that it is a read-only operation. The behavior of the 'request' parameter is also not described.

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 sentence that lists the output types, which is fairly concise. However, it could be slightly more structured (e.g., separating output description from source) but overall it is efficient.

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 object parameter and the presence of many sibling tools (including specific explore components), the description is incomplete. It does not explain the request format, how it differs from the sub-tools, or any response structure. This is a significant gap for a tool with a complex parameter.

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 has a single 'request' object parameter described only as 'Explore request', which is very vague. The description adds no clarification on how to structure the request or what fields it expects. While schema coverage is 100%, the description does not compensate for the lack of parameter detail.

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 retrieves Google Trends explore data, listing the specific analytics types (interest over time, by region, related queries, topics). It differentiates well from sibling tools like google_trends_trending or google_trends_explore_interest_over_time by specifying it returns multiple data types from a single request.

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 implies usage for keyword analytics but does not explicitly state when to use this tool versus the more specific explore sub-tools (e.g., google_trends_explore_interest_over_time). No guidance on prerequisites or when to choose alternatives is provided.

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