Start a bulk screenshot job from a CSV

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

No annotations exist, so the description carries the full burden and does well: it discloses the CSV contract (a 'url' column with full https:// URLs, other columns mapped to API option names), the asynchronous job model with an email notification side effect, and the paid-plan restriction. It omits failure behavior, row limits, and whether partial failures are tolerated.

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?

Four dense sentences, front-loaded with the action, then the input contract, then the return/follow-up, then the pricing gate. No sentence is filler.

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 no output schema, the description correctly covers the return value (job response with uuid) and the follow-up tools plus the email fallback. It leaves the async timing, row limits, and error semantics undefined, which is a modest gap for a job-submission tool.

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 the baseline is 3, but the description earns more by explaining the CSV row/column semantics that the schema only hints at — the 'url' column requirement and that extra columns become render options named after API parameters. The csv_path vs csv_content precedence is already in the 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?

States a specific verb and resource ('Uploads a CSV to start a bulk screenshot job') and the CSV format is a strong implicit differentiator from the sibling bulk_screenshots. It never names that sibling explicitly, so the differentiation is inferred rather than stated.

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?

Explains the input choice ('Pass either a local csv_path or the CSV text in csv_content') and routes the agent forward to get_bulk_status and download_bulk_results after the uuid is returned. It adds a real precondition ('Paid plans only') but gives no explicit when-not-to-use guidance versus bulk_screenshots.

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