Convert a bank statement PDF

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

Goes beyond the annotations by disclosing that conversion 'Uses pages from the BankConv account' (a billing/quota constraint) and that file outputs are 'saved next to the PDF' by default. Annotations already cover the read/write and open-world profile, and the description does not contradict them, though it says nothing about overwrite behavior, failure modes, or conversion limits.

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?

Front-loads the core action and the return/save distinction, then enumerates formats compactly. The format list is dense and duplicates the schema, but nothing is genuinely wasted.

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 specifies the returned transaction columns (date, description, signed amount, balance) and the file-save alternative. Remaining gaps are minor: no error/failure behavior, no note on how page consumption scales, and no relationship to get_transactions.

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 five parameters, including the output enum values that the description largely repeats verbatim. The description adds no format syntax, path semantics, or timeout nuance beyond the schema, hitting the expected baseline.

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: converts a PDF bank/credit card statement on this computer via BankConv, and names the concrete outputs (transaction rows or a saved file). It does not, however, distinguish itself from siblings like get_transactions or download_statement, which an agent might reasonably confuse with the 'transactions' output mode.

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?

Usage is implied ('a PDF bank or credit card statement on this computer') and enumerates format choices, but there is no explicit when-to-use / when-not-to-use guidance and no reference to alternatives such as get_transactions or download_statement. The agent must infer routing from the sibling names alone.

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