Find Reel links in web pages

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new context: Instagram has no anonymous search, so the tool is 'keyless' (no auth/credentials needed), and it discloses the return shape including that /p/ posts are listed separately and may be images rather than video. No rate-limit or pagination behavior is described, keeping it from a 5.

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?

Front-loaded with the core action, then clearly labeled 'Best for:' and 'Returns:' blocks. Every sentence carries information and nothing is repeated from the schema verbatim.

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?

No output schema exists, and the description compensates by describing the return (unique Reel URLs per page, posts separated). Combined with annotations covering safety and the reason the tool exists (no anonymous Instagram search), an agent has everything needed to select and call it correctly.

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% for both parameters, so the schema already documents the URL array and includePosts default. The description adds only the rationale for separating /p/ post links, not new syntax or constraints, so the baseline 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 and resource ('Collect Instagram Reel links from web pages') and enumerates the sources it targets (articles, newsletters, best-of lists, link-in-bio pages). It also distinguishes itself from the sibling reels_fetch by positioning that tool as the reader of the links this one discovers.

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?

'Best for: after a web search for a topic, pull every embedded or linked Reel out of the result pages in one call' gives an explicit trigger condition, and the reference to reels_fetch tells the agent which tool takes over next. The agent knows when to reach for this tool and what the follow-up is.

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