import_excel_to_import_set

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

Goes well beyond the annotations (readOnly=false, openWorld=true, idempotent=false): discloses that the original workbook is retained for auditability, that formulas and sys_* columns are rejected, that transform start is not verified, and the WRITE_ENABLED gate. These are exactly the side-effect and constraint details an agent needs.

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?

Dense and front-loaded, leading with the multi-step action and following with constraints. Every sentence carries meaning, though the run of caveats is packed tightly.

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?

For a 7-param, nested-object write tool with no output schema, it covers prerequisites, side effects, and validation restrictions well. It doesn't describe the returned Import Set handle/result, which would help the agent chain follow-up calls, but overall it's sufficient to invoke correctly.

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%, so the baseline is 3. The description reinforces the 'transform start is not verified' caveat and the .xlsx restriction but adds little parameter-level detail beyond what the schema already documents (sheet_name default, column_mapping example, 10 MiB limit).

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 specific verbs and resources (upload/parse .xlsx, create Import Set, insert staging rows, optionally request Transform Map run), and this compound workflow is clearly distinguishable from siblings like import_cmdb_data, create_import_set_row, and run_transform_map.

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?

Provides the key prerequisite 'Requires WRITE_ENABLED=true' and clarifies transform start is unverified, but it never states when to use this versus import_cmdb_data or create_import_set_row, nor any exclusions. Usage is implied rather than explicit.

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