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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety and scope profile is covered structurally. The description adds partial context about what the output contains (viral velocity, engagement, plays), but says nothing about ranking behavior, aggregation scope, or what happens when a username has too few videos.

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 capability statement front-loaded and the usage cue following; nothing is wasted. It could be marginally tighter, but every sentence 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 carries more of the burden of explaining return values, and it only lists metrics in passing without describing their structure. For a simple read-only analytics tool with fully documented params this is adequate, but not complete enough to guide an agent choosing among several TikTok analytics siblings.

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 all three parameters (username, limit, sort) are fully documented in the schema and baseline is 3. The description's mention of 'viral velocity' loosely mirrors the sort enum's viral_velocity option but adds no syntax, format, or default information beyond the schema.

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 ('Analyze TikTok video performance') and names the concrete metrics produced (viral velocity, engagement rates, play metrics). It does not differentiate itself from the very close sibling get_tiktok_top_videos, which an agent could easily confuse it with.

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?

Gives explicit trigger conditions: questions about TikTok video performance, video strategy, viral TikTok content, or which videos perform best. That is clear usage context, but it names no alternative tool and gives no when-not-to-use guidance, so the agent must infer when get_tiktok_top_videos is the better choice.

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