get_v1_media_by_url

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

Annotations already declare readOnly/openWorld/destructive, so the safety profile is covered. The description adds genuinely useful behavior beyond annotations: it is a live request to TikTok and is billed per call. It also discloses the downstream workflow (pass the returned id to comment tools), though it doesn't describe result fields or rate/error behavior beyond the schema's 400 note.

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?

Three tight sentences with zero waste. Purpose and sibling routing are front-loaded, followed by workflow, then billing/endpoint metadata.

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?

There is no output schema, but the description states what is returned and how to chain it. Combined with the fully documented param and the safety annotations, this is nearly complete; only concrete return fields or pagination detail are absent, which is minor for a single-resource fetch.

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% and the single `url` param already documents accepted link forms and the 400 behavior for non-media links. The description adds no parameter semantics beyond the schema, so the baseline of 3 is 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?

States a specific verb+resource ('Get a TikTok video by its link') and immediately distinguishes itself from the sibling get_v1_media_by_id by input type. An agent can route between the two without opening either schema.

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?

Explicitly names the condition that selects this tool ('when you have a tiktok.com URL') and the alternative with its own condition ('use `get_v1_media_by_id` when you already have the numeric video id'). Nothing is left to inference.

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