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

Annotations already declare readOnlyHint=true, so the safety profile is covered. Beyond that the description adds real behavior: the four possible status values, the shape of result for a clip chain vs. an Umzug import, and the semantics of waiting inside the call (with gewartet_s reported). It omits what happens on an unknown/expired job_id, keeping it out of the top band.

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?

Front-loaded with the core purpose, then the status enum, then return shapes, then the wait hint. Dense and mostly waste-free, though the two long result-shape enumerations make it longer than a minimal status tool needs.

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?

With no output schema, the description correctly takes on the burden of explaining the return value for two concrete job types and the wait behavior. It is nearly complete; only failure/unknown-job handling and the sibling overlap remain unaddressed.

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 description coverage is 100%, and both parameters (job_id and wait_s, with its 0-80 bound) are already fully documented in the schema. The description largely restates this ('wait_s (up to 80)'), adding only the rationale for using it over rapid polling, which is the expected baseline-plus behavior.

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?

States a specific verb and resource ('Get the status of a background job by job_id') with the domain of statuses enumerated. It does not, however, distinguish itself from the very similar siblings lab_job_status or lab_batch_status, so an agent must guess which of the three to call.

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?

Explicitly says to poll this 'after starting a long-running generate/export' and to prefer wait_s 'instead of polling in quick succession', which is actionable context. It stops short of naming the sibling alternatives (lab_job_status, lab_jobs_inflight) that would resolve the overlap.

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