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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful context that it returns both status and results and that output is paged, but it does not explain job lifecycle, readiness, expiration, or error behavior for an asynchronous job 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?

The description is a single front-loaded sentence that names the core purpose, the key parameter, and the paged behavior. It is efficient, though the compressed phrasing leaves important async-job context implicit.

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 simple read-only retrieval tool with three parameters and no output schema, the description covers the basic return concept ('status and results'). It remains incomplete for an async job tool because it does not explain possible statuses, polling expectations, or result shape despite the absence of an output schema.

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%, so the description must carry the burden of explaining parameters. It identifies job_id as referring to a previously started search and hints at paging, but it does not explain limit/offset semantics or clarify how job_id is obtained.

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 states a specific verb-resource pair: it returns status and results for a search identified by job_id. The phrase 'started earlier' distinguishes it from the sibling find_*/search_* tools that initiate searches, though it does not name those siblings explicitly.

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 phrase 'started earlier (job_id)' implies this tool is used after a search job has already been created, giving implied usage context. However, it does not explicitly state when to use this versus the sibling search tools, nor does it describe polling behavior or what to do if results are not ready.

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