scrape_job_status

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

Without annotations, the description discloses key behaviors: it returns status and pages, the wait parameter blocks until completion, and wait_timeout limits waiting. However, it does not cover error cases (e.g., invalid job_id) or confirm idempotency. Overall, it provides adequate transparency for a status-check tool.

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 description is very concise: a single sentence for purpose followed by a clean args list. No unnecessary words. Front-loaded with the main action. Structure supports quick scanning.

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?

The tool has low complexity (3 parameters, no output schema). The description covers purpose, parameters, and blocking behavior. It does not detail output format or error handling, but these are minor omissions. Overall, it is sufficiently complete for an agent to invoke correctly.

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 0%, so the description must explain parameters. It does so thoroughly: job_id is linked to previous crawl/batch jobs, wait blocks on 'running', wait_timeout sets max wait. This adds significant meaning beyond the schema's type and default values.

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 description clearly states the tool retrieves status and completed pages of a crawl/batch job. The verb 'Get' and resource 'status (and any completed pages) of a crawl/batch job' are specific. It distinguishes from siblings like scrape_crawl or scrape_batch, which initiate jobs, and scrape_cancel_job, which cancels.

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 description explains when to use the tool (after starting a crawl/batch job) and describes the parameters including their roles. It does not explicitly state alternatives or when not to use, but the context is clear enough for an agent to infer appropriate usage.

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