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 provenance (TikTok-generated), a meaningful empty-result state, and explicit constraints against polling, pagination, and fabrication. It does not state read-only status, auth requirements, or rate limits, which keeps it from a 5.

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?

Four sentences, each earning its place: purpose, provenance/disambiguation, empty-state handling, and operational limits. Front-loaded with the core action and free of padding.

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 no output schema, the description enumerates what the response may contain and warns of empty results, which is the key completeness gap for this tool. Minor omissions (auth expectations, explicit read-only framing) are the only shortfall.

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% and the query_id description already explains its origin (search_topics, browse_topics, trending_topics, related_topics) and what it is not. The description only restates 'one CSI queryId', adding no syntax or format detail beyond the schema, 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?

States a specific verb and resource ('retrieve available guidance for one CSI queryId') and enumerates the content types returned (hashtags, insights, script outlines, title ideas). It further distinguishes this from other tools by clarifying that the material is TikTok-generated, not produced by TokConnect.

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 clear when-not guidance: some topics have no guidance ready and the agent should report that rather than invent it or promise future generation. It also states there is no automatic polling or pagination. It stops short of naming a sibling as the alternative (e.g., search_topics to obtain a queryId), which the schema covers instead.

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