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

With no annotations, the description carries the full burden, and it does disclose two real traits: results come from a collection cache (so may be stale rather than live), and each call costs 2 credits. It does not say what is returned, how many items, or how failures/cache misses behave.

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?

Two compact clauses front-load the resource, then the priority rule and the credit cost — no waste. It is terse to the point of being cryptic, but nothing should be cut.

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 one-parameter tool it covers purpose, data source, and cost, which is a reasonable minimum given there is no output schema to lean on. Still missing: region/language scope, expected result volume, and any indication of what the response looks like.

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 a single keyword parameter with 0% schema description coverage, but the wording implies the keyword is the seed term from which rising queries are derived, which is useful framing. It adds no constraints (language, region, result count) beyond that implied meaning.

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 names a specific resource (Google Trends rising/breakout queries) and states its sourcing strategy (reads the collection cache, Breakout terms prioritized). Siblings like ledger_pulse and site_radar_latest are unrelated, so no differentiation is needed. The retrieval verb is only implied, but the resource is unmistakable.

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?

It gives no explicit when-to-use or when-not-to-use conditions, and names no alternative. The only usable signal is '读采集缓存' (reads the crawl cache), which hints at non-live data, but the agent must infer this rather than being told.

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