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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description's 'Read' is consistent. It adds some context about returned fields and the historical nature of versions, but it does not disclose error conditions, authorization needs, or any constraints around the version history.

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?

Two sentences with no filler. The action and resource are front-loaded, and each sentence adds distinct value: what is read and how history behaves.

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?

For a simple read tool with two required parameters and strong read-only annotations, the description is mostly complete: it identifies the resource, output facets, and history semantics. It leaves the exact meaning of 'blockers' and how to obtain claimVersionId implicit, but those gaps are minor for this operation.

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?

projectId is well described in the schema, but claimVersionId has no schema description. The description only indirectly identifies claimVersionId via 'exact version,' providing modest additional meaning. With 50% schema coverage, the description does not fully compensate for the undocumented parameter.

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?

Uses the specific action 'Read' with a clear resource: 'an exact version proposed through the controlled claim workflow.' It also lists what is returned (proof, scope, validity, blockers) and the closing phrase 'Historical versions remain history' differentiates it from a current-claim reader like read_business_claim.

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 clearly implies this is for reading a specific historical version within the controlled claim workflow, and 'Historical versions remain history' signals it is not for current claim data. It does not explicitly name the alternative read_business_claim or state when-not-to-use, but the context is clear enough.

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