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

The description goes well beyond the read-only, idempotent, open-world annotations by describing provenance tokens, a 15-minute validity window, cross-replica behavior, source_path mapping, unverified-model-data labeling, and an attribution-footer requirement. It also states a detailed data-accuracy contract covering derived metrics and forbidden inferences, giving the agent substantial behavioral context.

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 first sentence is a clear front-loaded purpose statement, but the rest is a long block of cross-tool chart_render and attribution rules. Much of that text is not about invoking tiktok_connector correctly, so the definition is overlong and poorly focused for its stated role.

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 action enum and params schema are rich enough to cover invocation details, and the description supplies extensive output-handling and data-integrity context. It is reasonably complete for an agent to use the connector safely, though it does not explain return shapes beyond the schema's action descriptions.

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 the action enum and params object are already fully documented in the schema. The description adds no parameter syntax or meaning beyond what the schema provides, making the baseline score appropriate.

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 opening sentence names the domain and resource precisely: TikTok account and video analytics, with concrete metrics such as profile stats, video performance, views, likes, shares, and comments. It is distinguishable from sibling connectors by platform, though it does not explicitly enumerate the multi-action scope that the schema provides.

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?

Usage is implied by the domain phrase 'TikTok account and video analytics', but there is no explicit when-to-use statement or comparison against alternatives such as YouTube or other social connectors. The conditional guidance about chart_render describes downstream handling, not when to invoke this connector itself.

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