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

Annotations already declare destructiveHint=false is not the case here (destructiveHint=true), non-idempotent, open-world behavior, so the safety profile is covered structurally. The description adds that this submits an asynchronous Builder task (implying a task handle rather than inline results), which is useful, but it omits auth requirements, rate limits, and what the task produces.

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 trigger is front-loaded, but the first sentence pads itself with four near-synonymous alias phrases (Instagram 帖子评论 / Instagram 评论 / Instagram post comments / IG 帖子评论信息) that repeat the same concept. Only two sentences total, so it is not bloated, but the redundancy costs it a point.

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?

This is an async task-submission tool with no output schema, so the description should tell the agent that results come back via a separate task-polling tool (scraper_task_status/result). It states a task is submitted but never explains the follow-up workflow or authentication, leaving an operational gap.

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 both parameters are already documented in the schema, including the posturl purpose and the file_name default. The description adds only that posturl maps to the ins_comment_by-posturl collector, so 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?

The second sentence states a specific verb and resource: it submits an Instagram post-comment collection Builder task and pins the collector identifier (ins_comment_by-posturl). This clearly separates it from siblings like instagram_profiles or instagram_reel, though the description never names a sibling explicitly.

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 trigger sentence states the context: use when the user wants Instagram post comments combined with collect/scrape/crawl/get/extract verbs. That is clear when-to-use guidance, but it offers no exclusions or named alternatives for related tasks.

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