get_trending

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

No annotations are provided, so the description carries full responsibility. It merely restates the tool's purpose ('Get trending products and rapidly growing stores') without disclosing behavioral traits such as read-only nature, pagination behavior, data freshness, or output structure. The description adds minimal value beyond the tool's name.

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 extremely concise: two sentences that immediately convey the tool's purpose and context. Every word earns its place, with no wasted text.

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?

Despite the sparse description, the tool has only three optional parameters and no output schema. The description covers the high-level purpose but lacks details on what 'trending' means algorithmically, how results are ordered, or the structure of the response. It is minimally adequate but leaves gaps for an agent.

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 input schema has 100% description coverage for all three parameters (page, category, per_page), so the schema alone adequately documents parameter semantics. The tool description does not mention parameters or add any extra meaning, placing it at the baseline of 3.

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 states the tool's purpose: 'Get trending products and rapidly growing stores.' This is a specific verb+resource combination that distinguishes it from sibling tools like search_products or search_stores, which focus on searching rather than surfacing trending items.

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 includes a usage context: 'Useful for identifying hot products, emerging niches, and fast-rising stores.' This provides clear scenarios for when the tool is appropriate. However, it does not explicitly mention when not to use it or compare with sibling tools like search_products, which might be preferred for targeted queries.

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