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

Annotations already flag a destructive, non-read-only mutation, and the description adds real behavioral value on top: it is asynchronous, returns per-task receipts and 'truthful admission failures', and warns 'submitted does not mean refreshed'. It stops short of explaining what the destructive refresh actually replaces or whether repeated calls are idempotent.

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?

Dense but front-loaded, opening with the verb/resource and closing with the required polling workflow; every sentence carries operational information. The 'Meta-wire-aligned alias of `tiktok_refresh_assets`' phrase is slightly cryptic internal jargon but still useful routing information, so waste is minimal.

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 an async mutation tool with no output schema, the description covers what an agent needs: the async task model, the polling siblings, the returned receipts/failures, and the warning that submission is not completion. The main 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?

There is one parameter (`connection_context`) with 0% schema description coverage, and the description never mentions it, so it fails to compensate for the coverage gap. The only hint is 'for the authenticated tenant', which loosely implies tenant scoping but gives no format or meaning for the connection_context pattern.

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 precise verb (refresh) plus a specific resource (TikTok asset snapshots) and enumerates the covered asset classes (pixels/audiences/identities/shops/TT accounts/apps/CTA portfolios) and scope (every active pull-enabled connection for the tenant). It also positions itself against siblings by naming the alias relationship to `tiktok_refresh_assets` and pointing to `tiktok_get_assets_status`, so an agent can distinguish it from the `assets_list_*` family without opening a 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?

Gives clear downstream context: poll the returned task_ref (or task_id) with `tasks_get_status`, and check per-task results plus `tiktok_get_assets_status` before preparing creation. It does not spell out an explicit when-not or explain when to prefer this over the aliased `tiktok_refresh_assets`, so the routing is implied rather than fully prescribed.

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