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

Annotations already declare this is a read-only, idempotent, non-destructive operation. The description adds useful context by saying it is 'Free, no key' and by hinting at ranking metrics, but it does not explain output shape, freshness limits, or how the optional limit affects results.

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 very short and front-loads the core resource and scope, with cost/auth information in a compact second sentence. The parenthetical metric explanation is somewhat cryptic, but there is little wasted wording.

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 tool with no output schema and an undocumented parameter, the description should explain what is returned and what 'limit' controls. It instead gives only a high-level label and does not help an agent understand the result set or parameter behavior.

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 has one optional parameter, 'limit', with bounds but no description text. The description does not mention 'limit' at all, so it fails to compensate for the 0% schema description coverage and leaves the parameter's meaning to inference.

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 identifies the resource and scope: 'Top rising keywords today' with a ranking basis of 'multiple vs. usual, number of platforms.' It does not explicitly distinguish itself from the related sibling keyword_trend, so sibling differentiation is missing.

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?

There is no guidance on when to use this tool versus keyword_trend, trending_items, or search_content. The phrase 'today' implies a current-trend use case, but no alternatives or exclusions are stated.

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