Extract data from a document

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

Annotations only say readOnlyHint=false and openWorldHint=true, so the description adds real value: it discloses the billing model (1 ParserBee page credit per page) and where results land (`data`). It does not cover failure behavior, page limits, or how multi-page documents are billed beyond the per-page statement.

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?

Four compact sentences, front-loaded with purpose, then input modes, then return location, then cost and prerequisite. No sentence is filler and the ordering matches how an agent needs the information.

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?

With no output schema, the description usefully states the result is in `data`, and it covers cost and the template_id prerequisite. It omits error/failure handling and async-vs-sync behavior, which are the only notable gaps for a document-processing tool of this complexity.

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 100%, so the schema already documents all three parameters and the baseline is 3. The description does add one thing the schema does not enforce: the either/or constraint between file_path and file_url, since neither is marked required. That is marginal added meaning over 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 (extract) and resource (structured data from documents) and narrows the domain to invoices, receipts, purchase orders, bank statements. It also names the mechanism (ParserBee Parser Template) and the required sibling artifact (template_id), so it is clearly distinguishable from the other ParserBee tools.

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?

Gives explicit input-mode selection (either file_path for local PDF/image or file_url for a public link) and routes the agent to list_templates to obtain template_id. It stops short of stating when-not to use this tool or what to do for unsupported documents, so it is clear context without full exclusions.

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