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

Annotations already declare openWorldHint=true and destructiveHint=false, so safety is partly covered. But readOnlyHint=false is unusual for a data-fetch tool and the description never explains why (credit consumption? scraping/rate limits?), nor does it mention failure behavior beyond what the schema's region note implies.

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?

One front-loaded sentence with zero filler; the resource and the input are stated immediately. Nothing to trim.

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?

An output schema exists and the input schema is fully documented, so return-value detail is not needed. However, for an open-world fetch tool with readOnlyHint=false, the description should at least signal cost/rate-limit/failure characteristics — that context is missing.

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 coverage is 100% and the schema descriptions are richer than the tool description (region retry advice, trim envelope behavior, WebVTT transcript format). The description adds nothing beyond 'by URL', so baseline 3 applies.

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?

Specific verb + resource: retrieves post data for a TikTok video or photo-post given a URL. The scope (single post by URL) implicitly distinguishes it from tiktok_profile, but the description never names that sibling or states the boundary explicitly.

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?

No when-to-use / when-not-to-use guidance and no alternatives named, despite a crowded sibling set (tiktok_profile, api_request, get_endpoint_schema). The only implied condition is 'you have a post URL', which the agent must infer.

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