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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, yet the description adds real context: counts de-duplicate each verified shard with expired leases rejected, final estimates exist only for completed jobs, and the payload exposes synthetic sampling parameters only. That privacy and aggregation detail meaningfully exceeds the annotations.

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?

Four short sentences, front-loaded with the core action before qualifications. No sentence is filler, though domain jargon like 'pi_chunk_v1' slightly taxes readability without adding 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, the description carries the return-value burden and does describe what comes back: verified progress, a final receipt, a completed-only estimate, and de-duplicated counts. For a single-parameter read tool this is largely sufficient, missing only guidance on retrieving the job_id.

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?

The single job_id parameter has 0% schema description coverage, so the schema supplies only type, format, and a UUID pattern. The description alludes to a 'job ticket' but never explains what job_id identifies or where the caller obtains it, leaving the parameter's meaning largely undocumented in prose.

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 and resource: read one contributor job ticket plus its verified progress or final receipt. This clearly distinguishes it from the write-oriented submit_network_job and from aggregate status tools. It stops short of naming a sibling explicitly, so the differentiation is implied rather than stated.

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 guidance or routing to alternatives. The note that 'only completed jobs contain a final estimate' tells the agent something about state but not about when to call this versus submit_network_job or network_status. Usage must be inferred from the verb 'read'.

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