preview_import

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

Beyond the read-only, idempotent, non-destructive annotations, it discloses format detection, automatic mapping suggestions, saved-profile matching, and validation through sample rows and errors. It could more explicitly confirm that no records are imported or profiles modified, but the preview framing is consistent with the annotations.

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 opening sentence front-loads the purpose, supported formats, mapping behavior, and outputs without unnecessary detail. The short Args list is easy to scan and every line adds invocation-relevant 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?

Together with the safety annotations and output schema, the description supplies nearly everything needed to select and invoke this moderately simple tool. The main remaining gap is whether exactly one of file_path or content is required and how supplying both or neither is handled.

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?

With 0% schema description coverage, the Args section documents all four parameters, including the four valid target values, the alternative file-content sources, and the purpose of profile_name. This substantially compensates for the bare schema, though it leaves the both/neither input-source cases implicit.

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 presents a pre-import preview that detects CSV or CAMT.053, proposes or applies a mapping, and returns normalized samples and errors. "Before importing it" and the references to saved profiles distinguish it from actual import and profile-saving siblings without needing to name them.

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 gives clear usage context: preview an export before importing, choose between a local path and conversation-supplied text, and optionally test a saved mapping profile. It does not explicitly route execution to import_transactions or state when previewing is unnecessary.

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