normalize_broker_csv

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

Discloses key behaviors: maps common column aliases, keeps only buy/sell rows (including DRIP as buys), cleans number formats, and returns both 'transactions' and 'skipped' lists with reasons. No annotations, so description bears full burden; adequately transparent.

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?

Well-structured with front-loaded purpose followed by details. Each sentence adds value, though slightly verbose. Could be trimmed without losing meaning.

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?

Given two parameters, no output schema, and sibling tools that are downstream, the description fully explains the output format (transactions, skipped list) and integration flow. No gaps remain.

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 0%, so description must add value. It explains that 'csv_path' accepts CSV/TSV/JSON file paths and 'rows' can be inline array, and mentions common column aliases. However, it does not detail the exact structure required for each row object, leaving some ambiguity.

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?

Clearly specifies verb 'normalize' and resource 'broker CSV', explaining it converts raw exports into transactions for other tools. Distinguishes from siblings by describing its role as a preprocessing step.

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?

Explicitly states when to use (raw broker CSV with mismatched headers) and directs output to downstream tools (calculate_acb, capital_gains_report, unrealized_gains). Lacks explicit when-not-to-use or alternatives, but context is clear.

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