collect_scrape_results

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

Discloses that results are saved to a file and a compact preview is returned, identical to search_* tools. Annotations indicate non-read-only and side effects, but description adds meaningful context.

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?

Two sentences front-loaded with verb+resource, then precondition. No wasted words; structure aids quick comprehension.

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?

Covers purpose, prerequisite, behavioral detail (saving, preview), and output comparison. Simple tool with output schema; description is fully adequate.

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?

Only parameter 'run_id' is documented in schema with clear description. Schema coverage is 100%, so baseline 3 applies; description does not add 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?

Clearly states 'Collect and save results from a completed background Apify scrape run.' Differentiates from siblings like start_* (initiate) and check_run_status (monitor status).

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 'The run must have SUCCEEDED — check with check_run_status first.' Provides clear precondition and alternative approach.

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