trending_discover

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

With no annotations, the description carries full burden. It discloses the expansion and filtering logic, the 12-month window, and the sorted output. Though it doesn't explicitly state read-only nature, the wording ('Discover', 'Returns') implies no mutation. It lacks details on rate limits or errors, but covers core behavior well.

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, front-loaded with the main purpose, then process, then output. No wasted words; every sentence earns its place.

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 simple read tool with no output schema, the description explains the process and return concept ('opportunities sorted by trend strength') but does not specify the structure of each opportunity (e.g., what fields are included). Also omits edge cases like empty results or invalid seed. Given no annotations, this is a notable gap but not severe for a 2-param tool.

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 covers both parameters with descriptions (seed keyword to expand, limit max). Description adds context by explaining the seed is expanded and filtered, reinforcing 'keyword' semantics, but adds little beyond schema for 'limit'. Baseline 3 is appropriate given 100% schema 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?

States a specific verb (Discover), resource (rising-trend keywords), and source (seed keyword's related keywords). Clearly differentiates from siblings like keyword_expand by focusing on trend filtering, and describes the process (expand, filter, sort) making it 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?

Implies usage for finding trending keywords but does not explicitly contrast with siblings like keyword_expand or trend. No when-to-use or when-not-to-use guidance is provided, leaving some inference to the agent.

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