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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=true. The description adds context about gap handling and explicitly states it never grants completion/approval. It doesn't contradict annotations, but it doesn't elaborate on the destructive or idempotent nature beyond the annotation flags, so it provides moderate extra value.

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 few dense sentences, front-loading the core action. It is not overly long but uses jargon ('extraction receipts', 'excerpt-budget blockers') that may obscure clarity. Nonetheless, it is efficient and gets the main point across.

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?

There is no output schema, and the description only hints at what it returns ('returned context/catalog revisions'). It doesn't explain the shape of contextRevision or the exact response structure, and the nested object parameters aren't fully described. For a workflow with these specifics, more detail on the return and parameter structure would improve completeness.

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 67% (projectId and idempotencyKey have descriptions; contextRevision lacks a top-level description). The tool description mentions 'returned context/catalog revisions' which alludes to contextRevision's role, but doesn't explain the inner fields (outputJobId, payloadHash). It adds some context but doesn't fully compensate for the missing schema description of the nested object.

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 clearly states the action ('freeze the extraction receipts into a new analysis context') with a specific verb and resource, and it distinguishes itself from siblings by describing a preparatory workflow step (after paginating and selecting quotes). It also lists what it never does (grants analysis completion or human approval), reinforcing distinct purpose.

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 gives an explicit precondition ('After paginating source documents and selecting exact quotes'), states what it resolves (legacy excerpt-budget blockers backed by complete versioned reading) and what it does not (partial/unsupported material keeps gaps). It also mentions the follow-up (submit analysis against returned revisions, then record page analysis). This is strong guidance on when and how to use it.

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