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

Annotations already cover the safety profile (readOnlyHint, destructiveHint false), and the description adds real behavioral context: result ordering, paging behavior, and a billing note ('normally not billed'). It does not describe pagination limits or error behavior, so not a 5.

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?

Very short, front-loaded with the action and scope, then the key non-obvious caveats. Every clause earns its place; the trailing endpoint path is compact and informative.

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 read-only list tool with annotation-covered safety and no output schema, the description compensates by naming the returned fields (job_id, status, created time) and the paging contract. Nothing needed to invoke it correctly is missing.

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 100%, so limit/offset/status are already fully documented in the schema. The description only restates 'with paging' and adds no syntax or filter semantics beyond what the schema provides, matching the baseline 3.

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 ('List') and resource ('the project's async capture jobs') with scope, ordering ('newest first'), and the fields returned. It is clearly distinguishable from the get/delete async job siblings.

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?

Adds a useful when-to-use signal by clarifying 'Does not process a document; normally not billed,' which separates it from the capture/submit tools, and 'with paging' signals the iteration use case. It never explicitly names a sibling alternative (e.g., get_async_job for a single job), so it stops short of a full 5.

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