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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses genuinely valuable behavioral traits: default date range, TikTok's 60-day retention, a one-to-two-day data lag, and the null-field condition for personal accounts or accounts under 100 followers. This is exactly the operational context an agent needs before calling.

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?

Three tightly packed sentences, front-loaded with what gets returned before the operational caveats. No filler, and the most decision-relevant information (the returned fields) comes first.

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 the return-value burden and does list the returned metric families, plus edge-case null behavior and freshness limits. It stops short of describing the response structure or the exact date format, but is otherwise complete for a read tool whose safety profile is covered by annotations.

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/endDate carry no description), and the description compensates by explaining the date window's default, retention ceiling, and freshness lag. The accountId/profileId semantics are already covered by the schema, so the remaining gap is minor.

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 opens with a specific verb and resource ('Return a TikTok account's daily metrics... and follower demographics') and enumerates the exact fields returned (video views, profile views, likes, comments, shares, followers; age, gender, country, city). It clearly marks this as account-level rather than post-level, but it never differentiates from the adjacent get_tiktok_analytics sibling, leaving one real ambiguity unresolved.

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?

It supplies useful context about the default window (last 28 complete days) and retention limits (60 days), which implicitly guides date-range selection. However, it never states when to pick this tool over get_tiktok_analytics or get_tiktok_video_insights, so the sibling boundary is left to inference.

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