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

With no annotations provided, the description carries the full burden and adds meaningful behavioral context: entities aggregate posts, repos, and releases across ten communities, and ranking is by cross-source momentum. The one-row-per-trend granularity is a useful disclosure. It does not mention authentication, rate limits, or explicit read-only status, which keeps it from a perfect score.

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?

Three sentences with no waste: the first defines the resource, the second explains aggregation and ranking, and the third routes the agent relative to a sibling. It is front-loaded and appropriately sized.

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 two-parameter list tool with no annotations and no output schema, the description covers purpose, aggregation semantics, ranking basis, and sibling routing. It does not describe the returned row fields, but that is a minor gap given the absence of an output schema and the simple list operation.

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 both the limit and category parameters are already fully documented in the schema. The description adds no parameter-level detail beyond what is structured, so the 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 states a specific verb and resource: trending entities ranked by cross-source momentum. It enumerates the kinds of entities (products, companies, libraries, technologies) and clarifies the row granularity. It also distinguishes itself from list_signals, so an agent can tell them apart without opening the schema.

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 an explicit routing rule: prefer this over list_signals when the user asks about trends or technologies, and use list_signals for individual posts. The alternative and the condition that selects it are named plainly.

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