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

No annotations are provided, so the description carries the full behavioral disclosure burden. It implies a read-only fetch and notes the returned content, but it does not disclose api_key/auth requirements, behavior for missing or incomplete jobs, or any error/rate-limit characteristics.

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 front-loaded sentence that states the verb, resource, and useful return detail without any wasted words. It is appropriately sized for a simple fetch operation.

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 tool with no output schema, no annotations, and 0% parameter description coverage, the description supplies only a high-level purpose and return summary. It omits job_id sourcing, api_key behavior, job-completion prerequisites, and error handling, leaving substantial gaps for correct 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 0%, and the description does not name or explain job_id or api_key. It indirectly frames job_id as identifying a parse job, but api_key's role and optional/default status are left entirely to the schema.

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 and resource: fetch the result of a parse job, and clarifies the return content with 'structured fields plus export links for accounting.' This clearly distinguishes it from get_balance, parse_invoice, and topup_link, though it does not explicitly name a sibling for routing.

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 'of a parse job' implies this tool is used after parse_invoice and with a job_id, so usage is somewhat inferable. However, it never states prerequisites such as job completion, when to prefer it over alternatives, or when not to use it.

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