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

The description discloses useful behavioral details beyond the sparse annotations: flexible column matching and error reporting for unreadable rows ('reported back rather than silently dropped'). This adds transparency about how errors are surfaced, though it does not specify the exact response format or idempotency behavior.

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 compact and efficient: three sentences, each serving a purpose. It front-loads the primary action, then provides instructions and error-handling behavior, with no redundant filler.

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 covers the core usage, supported formats, and error reporting, which is substantial for a tool with no output schema. It could be more explicit about the exact return structure (e.g., counts of imported/failed rows), but it is arguably sufficient for an agent to select and invoke the tool correctly.

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 parameters are already well-documented. The description adds value with concrete examples of column aliases (symbol/ticker, shares/quantity) and clarifies that csv_data must include the header row, enhancing understanding beyond the schema alone.

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 identifies the tool's function: importing a batch of trades from CSV into the Trading Journal. It names specific source platforms (Tradervue, TraderSync, Interactive Brokers, Degiro, generic), distinguishing it from sibling tools like log_trade (single trade entry) and update_trade.

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 provides concrete usage context: paste CSV contents including header, with flexible column matching. It implies this is for batch imports from exports, contrasting with single-trade tools, though it does not explicitly state when not to use it or mention alternative tools.

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