Parse a consolidated account statement

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

With no annotations, the description carries the full burden and does so well: it discloses local-disk, in-process parsing, no upload, password protection, automatic statement-kind detection, and the presence/absence of transactions by statement type. This is substantial behavioral context beyond merely saying 'parse PDF'.

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 opens with the core purpose, then adds scope, rationale, privacy, and password context in dense but non-redundant sentences. Every sentence earns its place and no fluff is present.

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 parse tool with no output schema, it communicates what the output will represent (holdings and optional transaction history) and covers inputs and constraints. It does not define the return structure or error behavior, a minor gap given the absence of an output schema, but the core call and chaining context are clear.

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 coverage is 100%, so a baseline of 3 applies; the description adds useful meaning by linking includeTransactions to the transaction-bearing CAMS/KFintech type versus the no-transaction NSDL/CDSL type. It also signals that password is commonly required, reinforcing the schema's password hint.

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 names a specific verb and resource — parse a consolidated account statement PDF — and explicitly enumerates the two handled statement types with their characteristics. It is clearly distinct from sibling analysis tools by framing this as the raw parsing step rather than portfolio analysis.

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?

It states when this is the only route (investor mutual fund holdings) and explicitly names the alternatives that do not cover it (INDstocks for equity/F&O/currency, AMFI for NAVs only). The kind detection also tells the agent it does not need to decide which parser to invoke.

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