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

With no annotations provided, the description carries the full burden. It discloses the exact output format (array with mid, title, type), that it works for a single keyword, and includes the token cost. It does not discuss error behavior or rate limits, but for a simple read operation this is reasonably transparent.

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 compact and front-loaded with the core purpose in the first sentence, followed by return format, usage guidance, and cost. Every sentence contributes useful information without redundancy or filler.

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?

The description covers the tool's purpose, output structure, and its place in the keyword-research workflow. It also references sibling tools (interest-over-time, interest-by-region, related-queries), providing strong context. It omits edge-case behavior (e.g., empty results, invalid keywords), but given the simple nature and output schema, it is sufficiently complete.

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 schema already covers the single keyword parameter with a clear description ('Keyword or phrase to get suggestions for'), giving 100% schema coverage. The description reinforces 'single keyword' but adds no new semantic details beyond what the schema provides, so the baseline score of 3 applies.

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 'Get Google Trends suggestions for a single keyword,' specifying the exact action and resource. It also details the return structure (array of topics/entities with mid, title, type), which distinguishes it from sibling tools like google-trends.interest_over_time or google-search.autocomplete.

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 explicitly advises using this tool 'to refine keywords before interest-over-time, interest-by-region, or related-queries calls,' giving clear context for when to use it. It does not explicitly mention alternatives or when not to use it, but the workflow guidance is strong.

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