parse_invoice

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

With no annotations, the description carries the full burden, and it does disclose one important non-obvious behavior: the extracted XML is written into a target folder rather than just returned. However, it says nothing about where that folder is, whether an existing file is overwritten, permissions, or error behavior on a malformed/non-PDF-A-3 input.

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?

A single sentence with no filler, front-loading the extraction action before the persistence side effect. It is appropriately sized for a one-parameter tool; there is simply very little content.

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 single-required-parameter tool with no output schema, the description covers the core action and the write side effect. It is still thin on the details an agent would want before invoking a tool that mutates a filesystem: destination folder, overwrite semantics, and failure modes.

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%, so the description is the only source of parameter meaning. It usefully implies the input is a PDF/A-3 file, but it never clarifies whether 'invoice_pdf_name' is a bare filename, a relative path, or an absolute path, nor whether the file must already be in a specific location.

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 specific verb pair (extracts XML, saves it) and a specific resource (embedded XML data in a PDF/A-3 file), which is enough to separate it from validate_invoice_pdf and validate_compliance. It stops short of explicitly contrasting itself with those siblings, so a 5 is not warranted.

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 statement of when to call this tool versus the two sibling validators, no prerequisites, and no exclusions. The use case is only inferable from the tool name and the mention of PDF/A-3 - which is implied guidance at best.

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