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

No annotations are provided, so the description carries the full burden. It does disclose the meaningful behavioral fact that several operations run asynchronously as jobs and that this returns both status and result, but it omits whether the result is only present on completion, whether the record is retained after completion, and how unknown/expired job_ids behave.

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?

A single front-loaded sentence with a parenthetical that earns its place by mapping job types to the sibling tools. No filler or repetition of the tool name.

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 one-parameter read tool with no annotations and no output schema, the description should explain the shape of the status/result (e.g. state values, when a result is available). It conveys the concept of async job polling but leaves the return contract, which has no schema to fall back on, undefined.

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 single parameter job_id has 0% schema description coverage, so the description must compensate. It only implies where job_id comes from (a job) and gives no format, source, or error semantics, leaving the agent to guess that it should be taken from a trigger_scan/expand_seeds/generate_content response.

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?

Specific verb+resource ("Check the status/result of a background pipeline job") with a parenthetical that enumerates the job-producing operations (scan, expand, generate, publish, index), which separates it from the siblings that trigger those jobs. It stops short of explicitly contrasting with list_jobs, which is the nearest ambiguous neighbor.

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 mention of background jobs implies this is a polling call made after a job is triggered, but the description never states when to use it versus list_jobs, nor that a job_id must first be obtained from a trigger_* call. Usage is inferable but not spelled out.

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