Fetch TikTok analytics

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

No annotations are provided, so the description carries the full burden. It reveals that the tool 'scrapes locally' and 'saves a time-series sample', indicating local data collection and persistence, but it does not disclose whether this is read-only, requires specific permissions, or has any side effects beyond saving data.

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 a single, concise sentence that front-loads the action ('Scrape') and specifies the resource and outcome with no unnecessary words.

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?

The tool has no output schema and no annotations, so the description should explain what the 'time-series sample' consists of and what the function returns or persists. The current description leaves the sample structure undefined and does not clarify whether this is a one-time operation or something repetitive.

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?

The input schema fully describes the single parameter 'account_id' with a pattern and descriptive text, so the schema itself provides adequate semantics. The tool description does not reference the parameter or add any additional meaning 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?

The description uses a specific verb 'Scrape' with a clear resource 'post metrics' and a concrete outcome 'save a time-series sample'. This distinguishes it from sibling tools like tiktok_like or tiktok_delete, which are obviously different operations.

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 implies this tool is for collecting TikTok post metrics, but it does not explicitly state when to use it over alternatives or provide any exclusions. There is no mention of contexts where this tool is preferred or inappropriate.

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