start_instagram_scrape

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

Discloses asynchronous background execution, immediate return of run_id, and need for subsequent monitoring and collection. This goes beyond annotations (readOnlyHint false, openWorldHint true) by explaining the async pattern, though it does not mention auth or rate limits.

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 concise sentences, front-loaded with the primary action. Every sentence adds value without redundancy.

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 the tool's async nature and the presence of sibling tools for monitoring and collection, the description adequately covers the workflow. It could mention what happens on failure or edge cases, but overall it is complete for its purpose.

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% with clear descriptions. The description does not add additional semantics beyond what the schema already provides, so baseline score 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?

Description clearly states it starts an Instagram profile scrape in the background and returns a run_id immediately. It distinguishes from the sibling tool search_instagram_profiles by specifying parallel use case.

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 tells when to use this tool instead of search_instagram_profiles ('when running multiple scrapers in parallel'), and provides a workflow: call check_run_status then collect_scrape_results.

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