Connect an Instagram account

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

Annotations already mark this as a non-read-only, open-world, non-destructive operation. The description adds substantial context beyond that: it opens a browser on the local machine, returns a sign-in link, connects every Facebook Page-linked Instagram account the user selects, waits up to wait_seconds, and describes the manual fallback when a page fails to load.

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 front-loaded with the main action and then layers in the Facebook Login behavior, waiting, and fallback. Every sentence carries useful information, though the final sentence is longer and could be split for easier parsing.

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?

For a two-parameter tool with no output schema, the description covers the important behavioral facts an agent needs: what starts, what the user sees, what gets connected, how long it waits, and what to do if the browser page fails. Nothing essential to invoking it correctly appears to be 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 50%: wait_seconds is documented in the schema, while open_browser is not. The description adds meaning to wait_seconds by explaining that the tool waits for the user to finish signing in, and it implies browser opening, but it never states what open_browser=false does, leaving part of the parameter semantics unaddressed.

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: starts the Meta sign-in to connect (or reconnect) Instagram professional accounts. It distinguishes the operation from sibling complete_connect by describing the fallback path, making it clear this tool begins the flow rather than completes it.

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 says when to use it (connecting or reconnecting professional accounts) and gives the exact condition for switching to complete_connect: when the browser lands on a page that does not load. It does not state prerequisites such as checking auth_status first or when not to reconnect, which keeps it below a 5.

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