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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds meaningful context: bounded page size, cursor invalidation behavior, the warning that complete refers to pagination rather than upstream sync coverage, and that it confers no permission to create. This is real behavioral disclosure beyond the structured fields.

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?

Purpose is front-loaded, followed by pagination semantics, then REQUIRED and an example. Mostly efficient, though the 'complete describes pagination, not upstream sync coverage or permission to create' clause is slightly defensive and could be tightened.

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 partially describes returns (compact bounded page, next_cursor, complete flag) and covers defaults, limits, and pagination discipline. It is complete enough to call correctly, though the connection_context parameter and exact page shape are left implicit.

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 0%, so the description must carry the load, and it documents three of four parameters well: limit (default 20, max 50), cursor (from the previous response, restart on rejection), and search (case-insensitive native id/name lookup). The connection_context parameter remains unexplained, though its pattern regex is largely self-describing.

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 cached TikTok Shops') and scopes it precisely to the authenticated tenant's Business Centers, even naming the upstream endpoint that populates the cache. An agent can immediately distinguish this from siblings like assets_list_business_centers or assets_list_tt_accounts.

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 explicit operational guidance: keep the same tool/filters/limit while following next_cursor serially until complete=true, and restart from page one on a rejected or stale cursor. It clarifies the meaning of 'complete' but does not explicitly name alternative tools (e.g. assets_refresh_all) or when to prefer a live refresh over the cache.

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