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

No annotations, so the description carries the burden: it discloses pagination semantics, the hasMore gate for nextOffset, and that records carry queryId values usable in further CSI calls. Does not describe rate limits, auth needs, or failure behavior, and there is no output schema to cover returns.

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 compact sentences, front-loaded with the core action, then sibling differentiation, then the pagination rule. No filler.

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 paginated read with no annotations and no output schema, it covers seed input, page scope, record contents, sibling disambiguation, and continuation. Missing only return-shape and error/rate context, which are minor for this tool class.

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%: limit, offset, and query_id are fully documented, including that query_id is not a video ID or username. The description adds only the nextOffset/hasMore relationship, so the schema does the heavy lifting and 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: fetch one page of TikTok's related topic records for a seed CSI queryId. Explicitly distinguishes from sibling related_queries ('Unlike related_queries, this is a paginated topic-record feed') and from similar_videos. An agent can route correctly without opening any 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?

Names the alternative it is not (related_queries, similar_videos) and gives continuation guidance ('Continue with nextOffset only when hasMore is true'). Does not state prerequisites or which seed-tool output to use beyond the schema, but the exclusions and pagination rule are explicit.

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