Parse a bank balance report (PDF)

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

Annotations already indicate a non-read-only, non-destructive, open-world operation. The description adds no further behavioral context (e.g., side effects on the file system, data storage, or return behavior), leaving the agent uncertain about what happens after the upload.

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 description is concise and front-loaded with the '[Premium]' flag, consisting of a single sentence with no wasted words. However, it under-specifies critical details, which prevents a higher score.

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 and the description does not explain what the tool returns after parsing, nor does it provide prerequisites or postconditions. Given the tool's simplicity, the description is incomplete for an agent to invoke it correctly without significant assumptions.

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?

With only 50% schema description coverage, the tool description should compensate for the undocumented bank_id parameter, but it does not. file_path is described in the schema, but the description adds no meaning to either parameter, especially failing to explain what bank_id refers to.

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 clearly states the action ('upload') and the resource ('bank balance report PDF'), making the tool's core purpose obvious. It is specific enough to be distinguished from general upload_document or approval_in_principle_scanning, though it could more explicitly describe the parsing output.

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?

No guidance is provided on when to use this tool versus siblings, nor are prerequisites like obtaining bank_id from get_banks mentioned. The description merely states the action without contextualizing the appropriate scenario.

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