tiktok_hashtag

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

With no annotations provided, the description carries the behavioral burden and usefully discloses pricing ($0.001 per video), pay-per-event billing to the Apify account, and that it runs on Apify. It does not cover authentication needs, rate limits, or data freshness, so it falls short of full transparency.

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 front-loaded with the main purpose and includes cost information early. It contains some marketing phrasing such as “ultra-competitive price” and a redundant title-like opening, but remains compact and readable.

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 six-parameter scraper with full schema descriptions and no output schema, the description supplies enough context about what data is extracted and the billing model. It does not mention validation mode or spending caps, but those are already documented in the schema.

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 input schema already explains all six parameters in detail. The description adds only the high-level idea of hashtag extraction and does not supplement parameter meaning beyond the schema, matching the baseline for high coverage.

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 states a specific verb and resource: it scrapes TikTok hashtag data and extracts videos, views, likes, comments, shares, audio details, and creator profiles. It clearly identifies the platform and hashtag-based scope, though it does not explicitly differentiate from any sibling tool.

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 “extract videos... by hashtag,” making it clear this tool is for TikTok hashtag research. However, the description does not say when to use it versus alternatives, nor does it provide prerequisites or exclusions.

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