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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds value by disclosing pagination (continue nextOffset until null) and an immutability constraint (preserve unrelated original entries, no inferred or replaced wording). This goes beyond annotations without contradiction.

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 single dense sentence that front-loads the core purpose, then adds constraints. It is efficient with no filler, though the multiple clauses could be easier to parse. Overall it is concise and well-structured.

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?

Given the tool has four parameters including a nested object and no output schema, the description is incomplete. It does not explain the required parameters, the meaning of maxFields, or what the response contains beyond vague references to field provenance and old text. An agent would likely struggle to invoke this correctly without additional context.

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%, and the description does not explain any of the four parameters. It hints at offset via 'nextOffset' but does not describe itemId, maxFields, or the assignmentRevision object structure. The parameter names are somewhat self-explanatory, but the description fails to compensate for the lack of schema descriptions.

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 tool reads exact target locations, old text, typed values, and field provenance for a current client-file assignment. This is specific and distinguishes it from other read tools like read_filling_field or read_client_original by focusing on assignment data.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It mentions that file inspection/filling is done with other tools, but does not name them or clarify scenarios where this tool is preferred. No exclusions or comparisons are given.

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