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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing further: it does not say what the run contains, whether the run must be claimed first, or anything about auth beyond what the schema's agent_key note already provides.

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 short, but this is under-specification rather than conciseness: a single dangling fragment with no front-loaded statement of what the tool returns or requires. Brevity here costs clarity.

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, no return-value documentation, an undocumented run_id, and annotations covering only the safety profile, the description is inadequate for an agent to call this correctly. It should at minimum explain what a run is and what the response contains.

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 coverage is only 50% — agent_key is documented in the schema but run_id has no description, and the tool description does not compensate by explaining what a run_id is or where to obtain it. The phrase 'the exact task you were assigned' gives only a faint hint about the identifier's origin.

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 reads as a fragment ('The exact task you were assigned, to finish it later') rather than stating a verb+resource. An agent can infer it retrieves a previously assigned run, but it never says 'retrieve/fetch a run' and does not distinguish this tool from claim_run, release_run, or next_task.

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?

There is no explicit when-to-use statement and no mention of alternatives like claim_run or next_task beyond the vague 'to finish it later'. The hint about resuming an assignment implies context but leaves the selection decision to inference.

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