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

Annotations already declare this as read-only, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description usefully adds that only permitted fields are exposed and that arbitrary private extraction metadata is withheld, but it does not clarify ordering, pagination, or whether this is a chronological audit trail.

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 two short, front-loaded sentences with no filler. Both sentences carry some meaning, though the first could be more precise about what 'correction fields' means in a history context.

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?

This is a read tool with no output schema, so the description carries more burden to explain what comes back. It says only that permitted correction fields are read and private metadata is excluded, leaving an agent unsure whether the result is a set of allowed fields or a chronological history of corrections.

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?

There is one parameter, and schema description coverage is 0%. The phrase 'for this invoice' implies an invoice identifier but adds no syntax, format, or constraint beyond what the schema already shows with invoice_id as a UUID.

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 states a verb and resource ('Read the permitted correction fields for this invoice'), but it does not match the tool name's emphasis on 'history' and never says what a correction history entry is. It also does not distinguish this from nearby invoice read tools such as get_invoice or get_invoice_review.

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 when-to-use guidance, no conditions under which another invoice-history or review tool should be chosen, and no prerequisites. The only usage-adjacent sentence is a privacy limitation, not a selection criterion.

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