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

Annotations already declare this as read-only, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds meaningful domain context beyond annotations: popularity values are TikTok's readings and must not be summed across days or described as monthly searches. That is an important caveat for correct interpretation, though it does not cover rate limits or response/pagination behavior.

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 definition is three sentences and front-loads the core scope before the routing detail and the popularity caveat. The example is compact and immediately useful. Nothing is redundant or padded.

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 a full output schema, complete input schema coverage, and annotations covering safety and openness, the description needs only to describe scope and notable caveats. It does that: it names the sibling source for id, summarizes the method-specific outputs, and warns about the most dangerous interpretation error around popularity values.

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 the schema already documents every parameter and method. The description still adds value with a compact example showing how id, method, days, and countries are combined in practice. It does not add much beyond the schema for the remaining parameters such as cursor or limit, which keeps it from a 5.

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 resource and scope: 'Everything about one search topic', then enumerates the exact data surfaces it returns (detail, popularity chart, demographics, related searches, guidance, videos). It distinguishes itself from the sibling demand_find_topics by explicitly defining id as the queryId produced by that tool, so an agent can route 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?

The description makes the prerequisite relationship explicit: id must come from demand_find_topics, not a video id or keyword. It also provides a concrete example call with method, days, and countries. It does not enumerate when to choose each method or when not to use this tool, but the context needed to invoke it correctly is clear.

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