pdf_form_xfa_acroform_flattener

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

With no annotations provided, the description carries the behavioral disclosure burden. It communicates that the output is static and immutable, guarantees 100% field content preservation, and discloses the 0.035 USDC cost. It does not detail edge-case behavior, but the key transformation is clear.

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 entire description is one efficiently packed sentence with no redundant words. It front-loads the core action, then adds the preservation guarantee and pricing context, all of which are useful for tool selection.

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 is sufficient for an agent to recognize what the tool does and that it costs money, but the payload structure is opaque and there is no output schema to clarify return behavior. An agent may know to select this tool but would need external knowledge to construct a correct payload.

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 coverage is 100%, but both parameter descriptions are generic ('Input parameters or JSON string payload', 'Base L2 USDC micropayment signature'). The tool description adds no further meaning about what the payload must contain, so it neither improves nor worsens the baseline.

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 uses a specific verb ('Flattens') and names precise resources (interactive AcroForms, dynamic XML XFA forms) plus the resulting output (static, immutable PDF pages). It clearly distinguishes this tool from form-parsing siblings like parse_pdf_form_fields.

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 phrase 'for optical validation' implies a use case, but the description does not explicitly state when to prefer this tool over alternatives such as parse_pdf_form_fields or pdf_page_rasterizer_highres. No when-to-use or when-not-to-use guidance is provided.

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