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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose two valuable facts beyond the schema — a Bearer sp_live_... API key requirement and a $0.02/call cost — but says nothing about data freshness cadence despite billing itself 'Real-Time', nor about pagination, rate limits, or whether the operation is purely read-only.

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?

A single compact line with the domain and audience front-loaded, followed by the auth and pricing constraints an agent needs before calling. No filler sentences, though the length is on the thin side for a paid external API.

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?

With three optional parameters, no output schema, and no annotations, the description covers what data exists and the cost/auth model but never indicates the shape or structure of the response. For a priced third-party API with zero structured safety metadata, more detail on return contents and real-time update behavior would be warranted.

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%, with each of the three optional parameters (limit range, apiKey fallback, keyword filter examples) fully documented in the schema itself. The description adds no additional meaning about limit defaults, filter semantics, or how keyword matching interacts with Korean-language terms, so the baseline 3 applies.

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 names a specific resource and scope: surging South Korean search demand keywords, traffic volume tiers, and breaking news triggers. It is clearly distinguishable from every sibling (github bounties, auctions, b2b leads, procurement bids, saas pain points, grants) by domain. It loses a point only because the operation is expressed as a noun-phrase tagline rather than an explicit verb, leaving 'retrieve vs. monitor' slightly implicit.

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?

Usage is implied only through the stated audience ('for e-commerce sellers and marketers'), with no explicit when-to-use, when-not-to-use, or named alternative among the seven siblings. An agent can infer this is the Korea e-commerce trend source, but nothing tells it how to choose between this and, say, query_saas_pain_points for adjacent market research.

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