eds_bulk_publish

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

With no annotations, the description carries the burden. It discloses the asynchronous behavior, immediate return of a job handle, and the need to poll for progress. It does not cover failure modes or permissions, but the core workflow is well explained.

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 with no filler: the first states purpose and scale, the second conveys the async workflow and follow-up action.

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 is an async job starter with two well-documented params. The description explains the immediate return and polling mechanism, making the workflow clear. It lacks details on edge cases, but that's covered by the job status tool referenced.

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 provides descriptions for both parameters, including an example for paths and default behavior for forceUpdate. The description adds no further parameter semantics, so 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 the action ('Start an asynchronous bulk publish job'), the scope ('from preview to the live production domain over many pages'), and distinguishes it from single-publish siblings like eds_publish_page by emphasizing bulk.

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 indicates this is for publishing 'many pages in one call' and provides a follow-up instruction to poll eds_get_job_status, but it does not explicitly mention when not to use it or name alternative tools for single-page publishes.

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