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

Annotations already declare readOnlyHint=false, openWorldHint=false, destructiveHint=false, idempotentHint=false, so the safety profile is partly covered. However, the description adds nothing about behavior — no mention of what parsing yields, whether checksum/digit validation occurs, or error handling for malformed MRZ. There is also a mild tension: 'parse' reads as a pure read operation while readOnlyHint=false and idempotentHint=false imply non-read, non-repeatable processing, which the description never explains.

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?

One front-loaded sentence that names the operation, the input domain, and the endpoint with no filler. It is efficient, though so terse that it borders on under-specification rather than optimal conciseness.

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, so the description should carry the burden of explaining what a successful parse returns (parsed fields, normalized values, validation results), and it does not. For a POST-based tool with no output contract and a schema that defers to an external resource, the definition is not complete enough for confident invocation.

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 reported at 100%, so the baseline is 3. The single body parameter is described only as 'JSON request body. See the AffixIO OpenAPI schema resource for the contract,' which is a pointer rather than real documentation; the description adds no field-level detail such as which MRZ formats or line lengths are accepted.

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 (parse) and resource (machine-readable zone / passport / ID card MRZ string), plus the underlying endpoint. It is clearer than most siblings, though it does not explicitly distinguish itself from the similarly named affix_aamva_parse (driver's-license barcode parsing).

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?

There is no guidance on when to use this tool versus affix_aamva_parse or other verification tools, no prerequisites (e.g., input must be a raw MRZ string of correct line length), and no exclusions. The agent is left to infer usage entirely from the name.

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