get_top_trends

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

No annotations are provided, so the description carries the burden of explaining behavior. It does indicate a read-only operation and reveals that data comes from RSS feeds, which is useful. However, it does not clarify how 'top' is ranked, whether there are operational constraints, or what kind of response shape to expect beyond the output schema.

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 a single, front-loaded sentence with no filler. It states the action, the resource, and the source immediately, making it easy for an agent to parse. It does not waste any words.

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 schema covers all parameters and an output schema exists, so the description can remain short. However, with 15 sibling tools including several trend-focused ones, the description does not help an agent determine whether this is the right tool to select. That missing selection context keeps it from being fully 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?

All three parameters are fully described in the schema (geo, type, limit) with defaults and constraints, so the description does not need to add much. It adds no parameter-specific meaning beyond what the schema already provides, which matches the baseline for 100% schema description coverage.

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 names the operation ('Get') and the resource ('top trends'), and adds a meaningful detail about the data source ('RSS trending feeds'). However, it does not differentiate this tool from closely related siblings like get_trends, get_ranked_trends, or get_trending_terms, so it stops short of 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?

There is no guidance about when to use this tool versus its many sibling tools. The description does not mention alternatives, exclusions, or conditions that would help an agent choose between get_top_trends and get_trends or get_ranked_trends. 'Using RSS trending feeds' implies a source, not a selection rule.

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