auto_import

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

Description explains the tool's behavior: uploads a file, auto-maps, and optionally imports or returns mapping. Annotations indicate non-destructive, open-world, which aligns. No contradictions but lacks details on error handling or permissions.

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?

Two sentences efficiently convey the core function and the dryRun variants without redundancy. Every sentence is essential and well-structured.

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 tool's simplicity and presence of output schema and annotations, the description covers main usage and dryRun distinction. It lacks guidance on file path interpretation or error scenarios but is adequate for the context.

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. Description adds value by explaining dryRun's purpose with a use case, but other parameters rely solely on schema descriptions, adding no new semantics.

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?

Description clearly states it uploads a file and auto-maps columns to a target entity, differentiating from siblings like import_csv (likely manual mapping) and execute_import (no mapping). The dryRun feature further clarifies the purpose.

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?

Description provides explicit guidance on when to use dryRun=true vs false, improving usage clarity. However, it does not explicitly state when not to use this tool or mention alternatives like create_mapping or execute_import.

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