tiktok_extract_post

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses that the tool extracts media (implying it is a read operation) and returns engagement metrics, but it does not mention any potential destructive side effects, authorization requirements, rate limits, or data freshness. The lack of annotations and limited behavioral detail keeps this at a mid-range score.

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 efficiently communicates the tool's purpose and deliverables without any wasted words. Every element earns its place.

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?

Given that the tool has only one parameter with full schema coverage, no output schema, and no nested objects, the description is complete enough for an agent to understand what the tool returns and how to invoke it. The specifics about media type (photos, video, audio) and nine engagement metrics cover the essential context.

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 schema already documents the single 'url' parameter thoroughly. The description adds no further syntax or formatting guidance beyond what the schema provides, leading to a baseline score of 3. No additional value is contributed for the parameter.

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 states the action ('extract'), the specific resource ('TikTok URL'), and lists the exact deliverables (unwatermarked HD photos, video download URL, audio, and nine categories of engagement metrics). This specificity and completeness distinguish it effectively from sibling tools like tiktok_download_post or tiktok_get_user_posts, which have different scopes.

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 the tool is used when you need unwatermarked media and full metrics from a single TikTok post URL. However, it does not explicitly state when NOT to use this tool (e.g., if only download is needed, use tiktok_download_post) or suggest alternatives for user-level data. The context is clear but omits exclusionary guidance.

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