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

With no annotations, the description carries the burden. It discloses useful behavioral traits: results are public summaries plus creation_snapshot_summary, and it explicitly says it does NOT call TikTok live APIs. It also clarifies scope to the current user. It does not explicitly say there are no side effects, but the 'List' framing and read-only-oriented wording largely cover that.

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?

The description is dense but well organized: purpose, use case, return behavior, parameter list, then example. Nothing is wasted, and the most important facts are front-loaded.

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 a read-only-style list tool with four optional parameters, no required params, and no output schema, the description supplies all operational essentials: scope, return content, non-live-API behavior, parameter ranges, and a runnable example. No annotation or output schema is needed to invoke it correctly.

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%, and the description fully compensates by documenting every parameter: status as a terminal-status filter, days with 1..365 and default 30, search as a campaign/adgroup/ad/id substring, and limit with 1..50 and default 20. The example reinforces how to combine them.

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 opens with a specific verb and resource: 'List recent TikTok create task history for the current user.' This clearly differentiates it from sibling list tools like tasks_list and tasks_latest, and makes the tool's scope obvious before any parameter details are introduced.

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 gives an explicit use case: 'Use this before comparing two launches such as...' and states what the tool returns, while noting it does not call TikTok live APIs. It does not name alternative tools or say when not to use them, so it stops short of full when/not/alternatives guidance.

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