import_transactions

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

The description states it's a write operation, matching readOnlyHint=false. Annotations already indicate it's not read-only and not idempotent, but the description adds no further behavioral context (e.g., side effects, duplication behavior, or error handling).

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 relatively concise with two short paragraphs. The first sentence is slightly redundant with the third, but overall it is front-loaded and contains no superfluous information.

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 the presence of an output schema, the description does not need to explain return values. However, it lacks details on batch size limits, error handling, or confirmation of successful import, leaving some uncertainty for a bulk operation.

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 baseline is 3. The description adds value by detailing required fields (currency, dataSource, date, etc.) and providing format examples (ISO-8601 date, BUY/SELL types), which helps beyond the schema.

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 states 'Import transactions into your portfolio' and specifies bulk import of buy/sell orders. This distinguishes it from sibling tools like create_activity (single transaction) and export_portfolio.

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 notes it is useful for bulk importing historical data or from other platforms, providing context. However, it does not explicitly state when not to use it or offer comparisons with alternatives like create_activity.

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