TikTok Video Stats API

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

The description goes well beyond the readOnlyHint and openWorldHint annotations by disclosing credit cost on live reads vs cache hits, the public-data boundary, and the platform-specific field naming convention. It also states read-only behavior explicitly. No contradiction with annotations exists.

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 compact and front-loaded with the key metrics, then adds return shape, field naming, cost behavior, and access boundaries. Each clause earns its place, and the only minor redundancy is 'Read-only' duplicating the annotation, which is not enough to penalize.

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 only two simple parameters and no output schema, the description sufficiently covers what an agent needs: the input URL, cache/cost behavior, output shape ('one object'), the fields returned, and the public-data restriction. No critical call-time information is missing.

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 url and cache are already well documented. The description reinforces the cache parameter by explaining the credit difference between live reads and cache hits, but it does not add substantial new parameter-level meaning beyond the schema's own examples and defaults.

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?

Description identifies the exact resource (a public TikTok video) and the specific metrics returned (views, likes, comments, shares, collects), then states 'Returns one object.' Sibling tools like tiktok_profile and tiktok_posts are clearly different in scope, so an agent can distinguish this tool without opening the 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?

The description gives useful context for when this tool applies: public TikTok video stats, with explicit limits ('Public data only: no bios, contact details or login-walled data'). However, it does not name sibling alternatives or state conditions for choosing this over tiktok_profile, tiktok_posts, or youtube_stats, so the usage guidance remains implied rather than explicit.

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