parse_portfolio_export

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

With no annotations, the description carries the full behavioral burden. It clearly discloses the key trait that no online broker access occurs, and 'parse and normalize' implies a non-mutating, read-only local operation. It does not cover error handling or return behavior, but the offline guarantee is highly valuable.

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?

Two concise sentences with no wasted words. The primary action is front-loaded, and the important offline constraint immediately follows.

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?

The description is adequate for a simple two-parameter parse tool, but with no output schema and no annotations, it leaves gaps around the return shape and the role of base_currency. An agent can make a reasonable call, but not with full certainty about expected output semantics.

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 50%: only 'path' is documented, while 'base_currency' has no explanation. The tool description does not mention base_currency or clarify how normalization uses it, so it fails to compensate for the schema gap.

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 uses a specific verb pair ('Parse and normalize') with a clear resource ('local broker portfolio export'). It also distinguishes itself by explicitly stating it never accesses brokers online, which sets it apart from online data-fetching siblings.

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?

The description gives clear context: this is for local export files, not live broker access. The explicit 'Never accesses any broker online' acts as an exclusion, though it does not name specific alternative tools for online scenarios.

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