Bulk: Run Status

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It details return contents: progress (processed/total), success/failure counts, per-row errors, and the final report CSV path. It also notes the 'when complete' condition, giving insight into possible incomplete states. This goes beyond a minimal status description.

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 two sentences, efficiently front-loaded with purpose and followed by specifics. No filler or repetition; every clause 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?

Given a single parameter, no annotations, and no output schema, the description fully explains what the tool returns and when, including progress, counts, errors, and report path. It is complete for a simple status tool and references the related bulk_execute tool for context.

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 input schema already describes run_id as 'The run_id returned by bulk_execute.' The description repeats this relationship without adding new syntax or format details. Since schema coverage is 100%, the baseline is 3, and the description does not elevate beyond that.

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's function: 'Get the status of a bulk run started by bulk_execute.' It specifies the resource (bulk run) and the action (get status), and references the specific start tool, which distinguishes it from sibling bulk tools like bulk_execute and bulk_run_resume.

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 implies usage context by stating it is for a run 'started by bulk_execute', signaling that it should be used after executing a bulk run. However, it does not explicitly mention alternatives or when not to use it, so it stops short of full guideline coverage.

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