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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered; the description adds real operational context beyond that — it is asynchronous, spawns one task per active connection, and returns legacy task_id values. It does not explain what the destructive flag actually affects (cache invalidation/overwrite cost) or how to poll the returned task_id, leaving a couple of behavioral gaps.

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, and the REQUIRED/OPTIONAL plus EXAMPLE blocks are well-structured and immediately scannable. The middle sentence is dense with product jargon ('legacy task_id', 'Agent Method clients', 'opaque task_ref'), but no sentence is wasted.

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?

There is no output schema and no schema descriptions, so the description carries the burden for an async, task-submitting tool. It states the return is a task_id but never tells the agent how to consume that id (e.g., the tasks_* polling siblings) and omits connection_context, leaving the workflow incomplete for a caller without prior product knowledge.

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 compensate. It does so well for 'days' (range 1..90, default 30, and the key clarification that it is a window length, NOT a date pair), but 'connection_context' is never mentioned, so half the parameters remain undocumented in both the schema and the 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 ('Async refresh of cached insights from the TikTok Marketing API') and explains the mechanism (submits one pull_tiktok_insights task per active connection). It also explicitly distinguishes itself from the sibling insights_query_consistent, so an agent can route without opening either 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 path explicitly ('Agent Method clients should follow the opaque task_ref returned by insights_query_consistent') and labels this the 'manual refresh compatibility path', giving a clear condition for choosing it. The guidance is framed around a specific client concept ('Agent Method clients'), which an arbitrary caller may not self-map cleanly, so it falls short of a fully general when/when-not statement.

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