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

The description adds behavioral context beyond the annotations: 'Keyless' indicates no authentication is required, which is not in the annotations. It also clarifies the data type (live snapshot) and includes the related news articles detail. Since the annotations already cover readOnly, idempotent, and openWorld hints, the description's additional notes on keyless access and the live vs historical distinction justify a 4.

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 two sentences, with the key point front-loaded in the form of a question. It is concise with no superfluous words. The differentiation from historical data is included efficiently. It isn't perfectly structured (the question style might be less formal), but it's effective and earns a 4.

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 tool is simple with only 3 parameters, all documented. Annotations cover safety (read-only, idempotent). The description includes return content (traffic floor, news articles), country-specificity, keyless access, and the temporal scope. It does not explain the response structure or error handling, but given the simplicity and no output schema, these are minor. It is sufficiently complete for an agent to use it correctly.

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 description coverage is 100%, so all parameters are well documented in the schema. The description mentions 'traffic floor' and 'news articles' which relate to output, not parameter semantics. It does not add any extra detail about parameter formats, defaults, or interactions beyond the schema. With high schema coverage, a baseline of 3 is appropriate.

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 current daily trending Google search terms for a country, with traffic floor and related news articles. It distinguishes itself from historical interest-over-time data, but does not explicitly name a specific sibling tool like pipeworx_trending. The verb 'returns' and resource 'trending search terms' are specific enough for a clear purpose, but the lack of explicit sibling differentiation holds it back from a 5.

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 provides an implied usage context: this is for live trending data, not historical. It explicitly says 'not historical interest-over-time data', which tells the agent not to use it for that purpose. However, it does not name alternative tools or provide explicit conditions like 'use this when you need current trends by country'. The guidance is present but minimal, earning a 3.

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