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

No annotations, so the description must carry the behavioral burden. It discloses that the returned codes feed other tools and that trending_topics and browse_topics ignore language — a non-obvious routing behavior. It does not document the return shape or pagination, but for a 0-param list tool this is solid.

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 resource identity, then usage, then a caveat about trending_topics. Tight and purposeful. Slightly dense but no wasted sentences.

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 no-param, no-output-schema list tool, the description covers identity, downstream usage, and an important exception. The only mild gap is not describing the return format, though for a language list this is largely predictable.

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?

Zero parameters, so baseline 4 applies. The description adds meaning by clarifying the semantics of the returned values (language codes) and their downstream use, going beyond an empty schema.

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+resource: list language options for TikTok Creator Search Insights (CSI) catalog. The prefix 'CSI catalog —' disambiguates from the many other TikTok list_* siblings like list_channels.

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?

Explicitly says where to use returned codes (search_topics, browse_topics) and where they are NOT applicable (trending_topics has no language parameter). It routes the agent away from wrong siblings, which is rare and valuable.

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