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

With no annotations, the description carries the full burden and does well: it discloses the returned fields, the pagination contract (nextOffset only when hasMore), and an eligibility prerequisite for the followers channel. It does not cover auth requirements or rate limits, but the behavioral core for a read-only paginated feed is present.

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?

Front-loaded with the core action, then dense semantic notes. Every sentence carries information (feed identity, field list, channel caveats, pagination rule), though the channel-by-channel caveats make it slightly listy rather than tightly prioritized.

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?

No output schema exists, so the description compensates by enumerating return fields and the pagination contract. Channel semantics and the trending/category routing note cover the main ambiguities of a 4-param, 12-value-enum feed browser; only auth/rate-limit behavior is left unstated.

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 coverage is 100%, so limit/offset/channel/language are already documented. The description does add channel meaning (content_gap is TikTok's feed not a computed score; followers refers to the connected account), which is genuine added value, but it also references a 'nextOffset' that does not exist in the schema (the parameter is 'offset'), creating a minor mismatch rather than clean enrichment.

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 and resource ('fetch one page of search topics from a selected Creator Search Insights feed') and explicitly negates adjacent content ('not videos or creators'), so an agent can distinguish it from search_videos/creator_posts without opening a 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?

Gives real usage context: content_gap and followers channel semantics, the note that trending/category channels route to the same feed as trending_topics, and the rule to pass nextOffset only when hasMore is true. It stops short of an explicit 'use this instead of search_topics/topic_detail when...' routing statement, so it is clear context rather than full when/when-not guidance.

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