Get the status of a bulk verification job

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

With no annotations, the description carries full burden. It discloses that this is a polling operation, lists the returned fields, and implies a read-only nature. It does not mention error behavior or rate limits, but for a simple status endpoint this is adequate.

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?

Exactly two sentences: the first defines the action and output, the second provides the workflow. No fluff, front-loaded verb, and every word adds value.

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?

For a tool with one parameter and no output schema, the description covers the returned fields (status, percent progress, processed count, valid/invalid/risky summary), when to call it, and the next step. It is fully sufficient for an agent to use 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?

The schema already fully describes job_id as 'The job_id returned by submit_bulk', with 100% coverage. The description merely restates 'by its job_id', adding no new parameter meaning, so the baseline 3 applies.

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 'Fetch the current status and progress of a bulk verification job by its job_id', using a specific verb and resource. It distinguishes itself from the sibling get_job_results by focusing on status/progress rather than final results.

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?

It explicitly instructs to 'Poll this after submit_bulk until status is completed, then call get_job_results', naming both a predecessor and a successor tool. This provides clear when-to-use guidance and an explicit alternative.

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