import_mapping

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

The description says 'Save column mapping', a write to the import job, while annotations declare readOnlyHint=true. An agent following the description would treat this as a mutation, contradicting the declared safety profile. No compensating detail (whether mappings are overwritten, whether they persist until execution) is given.

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?

Three short sentences with the action front-loaded and the workflow hint last; nothing is redundant. Slightly more compact would be ideal, but every sentence carries signal.

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?

No output schema exists, and the description does not say what is returned or whether the mapping persists until import_execute. For a small 3-parameter tool the purpose and timing are covered, but the mutation semantics and result are left implicit.

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 100%, including the columnMapping nested object and companyId override, so the schema carries parameter meaning. The description only restates the mapping's direction (CSV column names to Storno field names) without adding new syntax or format detail.

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?

States a specific verb and resource ('Save column mapping for an import job') and adds what the mapping does ('Maps CSV columns to Storno fields'), which distinguishes it from siblings like import_preview and import_execute without naming 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?

Explicitly places the call in the workflow: 'Call after reviewing the preview to confirm or adjust mappings before executing.' The sequencing versus preview and execute is clear, though the sibling tools are not named and no exclusion case is given.

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