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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false. The description goes further by disclosing auth scoping, the required history:read scope, pagination behavior ('bounded scan/continuation'), and a genuine data-quality caveat ('unknown provenance and NULL own spend/creator settlement remain explicit'). That is meaningful behavioral context beyond the structured hints.

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?

Front-loaded with the access scope, which is good, but the prose is dense jargon-heavy fragments, and the trailing laundry list ('No wallet selector, public report/share link, model prompt, research, source fetch, signer, purchase or mutation authority') spends a full sentence on negatives of low routing value.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. The remaining gaps are the undocumented 'id' parameter and the lack of any sibling routing, which for a member of a large history_* family leaves the agent under-informed about correct invocation.

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 parameter burden, and it does not. The single 'id' parameter is never mentioned; only the schema pattern (^prv_[a-f0-9]{64}$) hints at its format, and the description adds no explanation of what identifier to pass.

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 identifies the resource ('completed private jobs in the current store') and scope ('private data for this authenticated caller only'), and the title adds 'Read one of your completed private results'. However the verb is absent from the description and it never distinguishes this detail tool from siblings like history_private_jobs_list or history_private_jobs_export, leaving the agent to infer the single-record semantics from the name alone.

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?

It states one prerequisite ('explicit history:read required') and a negative constraint ('No wallet selector'), which is useful. But it gives no when-to-use guidance relative to the many sibling history_* tools (list vs export vs detail vs owned_read), so the agent cannot route between them from this text.

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