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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered; the description goes further by disclosing data retention (60 days), ingestion lag (1-2 days), the default window, and null-field behavior for personal accounts and accounts under 100 followers. These are concrete data-quality traits an agent cannot get from the annotations. It still doesn't mention rate limits or pagination.

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 tightly packed sentences: the first states purpose and payload, the second front-loads the window default, retention, and null caveats ahead of any detail. Every clause carries operational value with no filler.

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 appropriately enumerates the returned metric categories and the null-field limitation, and annotations cover the read-only/open-world profile. An agent has enough to call it correctly, though a note on date-range bounds interaction or result granularity 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 only 50% (startDate and endDate have no schema descriptions), but the description compensates by defining the date window as UTC and specifying the default fallback of the last 28 complete days. This gives meaningful semantics for the two undocumented date parameters, though it doesn't clarify the format (already in schema) or behavior when only one bound is supplied.

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 (Return) and resource (a TikTok account's daily metrics), then enumerates the exact metric families (views, likes, comments, shares, followers) and demographic breakdowns. It is implicitly distinguishable from video-level siblings like get_tiktok_video_insights because it scopes to the account, but it never names or contrasts a sibling explicitly.

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 operating context (default window of 28 complete days, 60-day retention) that implies when the tool is applicable, but it never states when to choose it over get_tiktok_analytics, get_tiktok_video_insights, or get_tiktok_creator_info. Usage is left to inference from the account-level scope.

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