search_instagram_profiles

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

Description adds behavioral context beyond annotations: remote scraper, time range, result storage method, and that only a compact preview is returned. Contradicts nothing in annotations.

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 sentences are concise, front-loaded with purpose, behavioral context, and guidance. No wasteful or redundant phrasing.

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?

With output schema present, description need not detail return values. It covers the scraping process, timing, and result handling. Lacks mention of error handling for missing profiles, but otherwise complete enough for a tool with good annotations and low parameter count.

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%, so baseline is 3. Description restates schema information for both parameters without adding new semantics. It does not explain the compact preview format or details beyond schema.

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 verb 'Fetch' and resource 'public Instagram profile data' with specifics (follower counts, bio, recent posts). It distinguishes from siblings like start_instagram_scrape and read_saved_results by implying this tool provides initial fetch and compact preview.

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 mentions the remote scraper runs 30s–few minutes, results saved to JSON, and suggests using read_saved_results for full dataset. Provides clear context but does not explicitly exclude alternatives like start_instagram_scrape.

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