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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds that results are scoped to a time period, but says nothing about failure modes (private/nonexistent accounts), data freshness, or return shape.

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, front-loaded with the core capability followed by usage triggers. No filler, though the second sentence slightly repeats the first's subject.

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 simple read-only stat fetcher with fully documented parameters, this is nearly complete; the metric list and period scoping cover what the agent needs. With no output schema, a brief note on response structure or account-not-found behavior would close the remaining gap.

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 coverage is 100% with enum values and defaults documented for period and metric_focus, so the schema does the heavy lifting. The description mentions time period and growth metrics but adds no syntax or behavioral detail 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 ('Get TikTok account statistics') and enumerates the metrics returned (followers, likes, posts, growth). The 'TikTok' qualifier distinguishes it from the generic get_account_stats, but it does not differentiate from close siblings like get_tiktok_growth_summary or get_tiktok_content_breakdown.

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 clear usage context: when someone asks about a TikTok account's performance or wants a stats overview. It stops short of stating when to prefer a sibling tool (e.g. growth-only or content-specific queries) or any exclusions.

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