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

Annotations already mark this as a non-read-only, non-idempotent, non-destructive write with open-world behavior. The description adds important context beyond annotations: page-credit consumption, the server never buying credits or changing plans, possible automatic replenishment on annual plans, and returned document id plus remaining quota.

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 purpose and write nature are front-loaded, followed by operational constraints and billing behavior. Every sentence carries useful information for correct invocation, and the size-limit alternative is stated directly.

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 appropriately states what is returned: the new document id and remaining quota. Together with the size limit, billing caveat, and sibling reference, it gives an agent enough to call the tool correctly.

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 all four parameters are already documented. The description adds the file-size limit and confirms base64 content, but does not add syntax or meaning for parser_id, file_name, or remote_id beyond 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 (upload), resource (one small file), format (base64), and action (parse it) tied to a parser. It explicitly distinguishes itself from docparser_fetch_document_from_url for larger files, so an agent can select it without opening sibling schemas.

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?

Provides a clear condition for using this tool (files up to about 2.3 MB) and names the alternative explicitly for larger files. It also warns to check billing settings before use when credit replenishment could matter.

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