TikTok profile data

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state whether the tool is read-only, what happens on invalid URLs, whether it handles pagination, or any rate limits. It only lists output fields, which is insufficient for the agent to anticipate side effects or error behavior.

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, front-loaded sentence that directly states the resource and data fields. There is no wasted language or redundancy. It is appropriately sized for a simple data retrieval tool.

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 tool with one parameter and no output schema, the description adequately identifies the output but falls short on broader context. It does not specify return format, error handling, or usage scenarios. Given the lack of annotations and output schema, the description should provide more behavioral and usage context to be fully complete.

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 already describes the single `url` parameter as 'TikTok profile URL' with format URI, resulting in 100% schema description coverage. The tool description adds no additional meaning about the parameter (e.g., expected format, examples, or constraints), so it does not exceed the baseline of 3.

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 clearly identifies the resource (TikTok profile) and the specific data fields returned (bio, followers, following, video count). It distinguishes from sibling tools like web_data_tiktok_posts or web_data_instagram_profiles by naming the platform and profile scope. However, it lacks an explicit action verb (e.g., 'gets' or 'retrieves'), relying on the title and context to imply data retrieval.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It only states the output, leaving the agent to infer usage from the name and siblings. There is no mention of when a profile URL is needed or how this differs from web_data_tiktok_posts/comments.

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