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

No annotations are provided, so the description carries the full burden, and it succeeds. It discloses the fallback behavior, the conditions that trigger it, the thumbnail/still_url/transcript behavior, and the fact that the tool is free.

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 dense but efficient, front-loading the main purpose and then covering fallback behavior and the alternative. The fallback clause is somewhat run-on, but every part adds information and there is no filler.

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 an output schema exists and the description already explains the important fallback semantics, the agent has enough to select and invoke the tool. The main remaining gap is parameter-level detail, especially api_key, which is notable but not crippling given the small parameter set.

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 0%, so the description must compensate for the lack of parameter documentation, but it never explains api_key or hook_id. It provides useful domain context about hooks, player_url, and still_url, yet leaves api_key's purpose and whether it is truly needed ambiguous despite the optional default.

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 deliverable: official TikTok or Instagram embed HTML for a hook, with a clear distinction from the plain iframe path via player_url. It also explains the fallback output mode, so an agent can tell exactly what this tool produces.

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 gives concrete usage context: use this for official embed HTML, and use player_url instead when a plain vertical iframe is needed. It also spells out when the fallback kind applies, e.g., embedding disabled or an old photo post. It does not enumerate other sibling tools, but the provided alternative is explicitly named.

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