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

The annotations already establish that this is a safe read-only, closed-world lookup. The description adds meaningful behavioral context beyond them: it describes what data is included (latest day, category column, rank, prior-year line, clue) and explicitly states that raw search-volume values are omitted, though it does not cover error behavior or rate limits.

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-loads the core concept before adding terms-of-use information. The bilingual repetition is slightly redundant but not wasteful enough to outweigh the efficient structure.

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?

An output schema exists, annotations cover the safety profile, and the single parameter is fully documented. The description still supplies useful semantic context about the returned data and the omission of raw search volumes, leaving only minor gaps around how this tool relates to its siblings.

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?

There is only one parameter, and the schema already documents it at 100% coverage with an example. The description reinforces that the input is a shopping search keyword, but it adds little syntax or format detail beyond the schema, so the baseline 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 identifies a specific resource: one shopping keyword from the trend shopping surface, shown on the most recent day it appeared, with rank/column context. It is much more concrete than a tautology, but it does not explicitly distinguish itself from the sibling tools 'repository' and 'today'.

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 that this tool is for looking up a single keyword, but it gives no explicit when-to-use guidance, no exclusions, and no comparison to the available alternatives 'repository' and 'today'.

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