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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds real context beyond them: pagination semantics, a caution to "preserve all unrelated original entries," and a prohibition on inferring or rewording values. These are non-obvious behavioral constraints that guide correct use.

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?

Three sentences, front-loaded with the core read purpose, then pagination, then constraints. No redundant padding, though the resource enumeration in sentence one is dense enough to slow reading.

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?

The description does sketch the returned payload (locations, old text, values, provenance) in place of an output schema, which is helpful, and it covers pagination. But with a required nested revision object and 0% parameter documentation, it omits enough that an agent could still mis-invoke it.

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 carries the full burden, and it largely fails. It names "nextOffset," which does not match the schema parameter `offset`, and ignores itemId, maxFields (capped at 4), and the nested assignmentRevision object with its outputJobId/payloadHash requirements. The naming mismatch is actively misleading.

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 (Read) and a concrete set of resources: bounded exact target locations, old text, typed values and field provenance for a current client-file assignment. An agent can distinguish this from siblings like read_client_original or read_filling_field, though the phrasing is dense and jargon-laden. The `_assignment` focus is clear but not sharply contrasted against every nearby reader.

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?

Provides a pagination instruction ("Continue nextOffset until null") and a boundary ("File inspection/filling is performed with the customer's file tools; values must not be inferred"), which implies this tool only reads and does not write. However, it never states when to use this vs. a sibling reader or what precondition (a prepared client-file assignment) must hold, leaving selection to inference.

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