execute_import

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

Annotations indicate readOnlyHint=false suggesting mutation, and the description confirms this by saying 'uploads and starts an import'. It adds details beyond annotations: file read from disk, absolute path required, returns import object with importId, status starts SCHEDULED, and file limits. This provides useful behavioral context without contradiction.

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 three sentences long, each serving a purpose: stating the main action, providing operational details, and specifying constraints. It is front-loaded with the key operation and wastes no words.

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 has 4 required parameters, an output schema, and several sibling tools, the description covers the core functionality, input requirements, return value, and status polling. It is mostly complete but could explicitly mention that the mapping must be created beforehand (implied by 'using an existing mapping').

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 fully documented in the schema. The description adds minimal extra meaning: it mentions absolute path for filePath and implies that entityName must match list_entities entities. This is adequate but does not significantly enhance understanding 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 the tool uploads a CSV/XLSX file and starts an import using an existing mapping. The verb and resource are specific, and the explanation of returning an import object with importId distinguishes it from siblings like import_csv which may not use existing mappings.

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 context by specifying to pass an absolute path, to poll get_import_status or use wait_for_import, and file format limits. However, it does not explicitly contrast with siblings like auto_import or import_csv, nor does it state when not to use this tool or mention prerequisites like needing to create a mapping first.

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