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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds that the SEO lists are 'public' and that partners data is a leaderboard, which is modest extra context. It discloses nothing about rate limits, data recency/staleness, or the note-reporting behavior for clamped limits (that lives only in the schema).

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 sentences, capability list front-loaded before the example, with zero filler. Slightly more could be trimmed, but the compact example earns its place by showing the method/value contract.

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 11 fully documented parameters, an output schema present, and rich annotations, the description only needs to frame the method families — which it does. Remaining gaps (no cross-references to reference method=creative_markets required for partners markets, no output-shape hint) are carried by structured fields.

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 100%, so every parameter including method, country, sort, period and page is already documented inline with its method-scoped meaning. The description's example does illustrate one valid method/country/sort triple, but adds no syntax or semantics beyond the schema. Baseline 3 applies when the schema does the heavy lifting.

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 the resource (TikTok Creative Center) and enumerates the three data families it exposes — top videos by market, SEO inspiration lists, and Creative Partner agency leaderboards — matching the four method enum values. An agent can tell what it fetches, but nothing distinguishes it from siblings like video_top_selling or category_trends, which likely cover adjacent trending content.

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?

The worked example ({"method":"top_videos","country":"JP","sort":"engagement"}) implies how to invoke it and the per-method parameter pairing is only discoverable by reading the schema. There is no statement of when to choose this over sibling trending tools, no prerequisites, and no exclusions — guidance is implied rather than stated.

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