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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds non-obvious context: the data is cached, rows are augmented with computed counts, cursors can be rejected/expire requiring restart, and 'complete' does not imply upstream sync coverage or creation permission. Only freshness/staleness of the cache is left unstated.

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 purpose before pagination mechanics, and each paragraph has a distinct job (what it lists, return shape, pagination, caveats). It is somewhat dense and longer than strictly necessary, but no sentence is 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?

No output schema exists, and the description compensates by describing the return shape (compact bounded page, next_cursor, complete flag) and pagination semantics. Zero required parameters is clear, and the only real gap is the undocumented connection_context parameter.

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 0%, so the description must carry parameter meaning, and it does: limit (default 20, max 50), cursor (from previous response, can be rejected/old), and search (case-insensitive native id/name lookup). It omits connection_context entirely, which is the one parameter left undocumented in both schema and description.

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 ('List cached TikTok Business Centers') plus scope ('for the authenticated tenant, across every connection') and notes the enrichment fields (advertiser_count, pixel_count). Clear and specific, but it differentiates only implicitly from siblings like assets_list_ad_accounts or assets_list_pixels by resource name alone, with no explicit contrast.

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?

Strong operational guidance on pagination protocol (keep same tool/filters/limit, follow next_cursor serially until complete=true, restart page one on a rejected cursor) and a useful clarification that complete refers to pagination rather than sync coverage. However, it never states when to choose this tool over sibling asset-listing tools, so alternative selection is left to inference.

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