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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description's real added value is the asynchronous model: the call merely queues the job and results must be fetched separately with get_tt_trend_analysis. It also surfaces the batch cap of 5. It does not explain why destructiveHint is true for what reads as an analysis/queue operation, which is the one gap an agent might trip on.

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?

Two tight sentences with the [write] marker and the output-retrieval path front-loaded — no filler. Slightly dense with parentheticals, but every clause carries information.

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 correctly compensates by naming get_tt_trend_analysis as the result path and flagging the async queue behavior. The only shortfall is silence on the optional brief/language controls, which affects output tailoring.

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 the parameters. It does well for aweme_ids (origin tool and max 5 items) but says nothing about the optional `brief` and `language` parameters, leaving two of three 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?

The description names a concrete verb and resource — send TikTok posts (aweme_ids) to content analysis — and explicitly scopes it as the TikTok specialization of analyze_trend_media. An agent can tell it apart from the generic analyze_trend_media and from list_tt_trends/list_tt_videos 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?

It states the prerequisite (aweme_ids must come from search_tt_videos), an explicit limit (at most 5), and the follow-up tool to call (get_tt_trend_analysis). The whole call sequence is spelled out, leaving nothing to inference.

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