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

No annotations are provided, so the description carries the full behavioral burden. It hints at async completion semantics ('Returns the results when it is finished'), but does not say what is returned while the job is still pending, what happens on failure or timeout, or whether polling is required — all critical for a job-status tool.

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 short, front-loaded sentences with no filler; the core action leads and the return behavior follows. Slightly terse rather than padded, which is appropriate, though it leaves no room for the missing detail noted elsewhere.

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 annotations, no output schema, and a 0%-coverage input schema, the description is the only source of information and it omits the job_id contract, pending/failure states, and return shape. For a polling tool in a large toolset, this leaves the agent under-equipped to call it correctly.

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 0% and the description never mentions the single parameter job_id — not its format, where it comes from, or whether it is required. With one undocumented parameter, the description does not compensate for the schema gap.

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 ('Check') and resource ('a job'), and scopes it to jobs 'started by any other tool', which distinguishes it from sibling tools that do the work itself. It stops short of naming any specific sibling start tool, but the async-job-worker role is unambiguous.

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?

'Check a job started by any other tool' implies the usage context (call this after some other tool launched an async job), which is genuine guidance. However, it says nothing about when not to use it, how to obtain the job_id, or how often/when to poll versus waiting for a push.

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