import_data

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

With no annotations, the description carries the full behavioral disclosure burden. It does an unusually good job: formula-injection blocking, the 200,000-cell write ceiling, hazardous-workbook refusal, auto-backup, atomic verified save, and refusal while the workbook is open in Excel are all disclosed. The main gap is that it does not state whether existing cells in the destination range are overwritten or how 'hazardous' is defined.

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 dense but every sentence carries distinct, non-obvious information. Purpose is front-loaded, and the safety and failure behaviors are listed without redundant filler.

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?

The tool has 13 parameters and no annotations, so the description needs to be far more complete. It leaves the required path unexplained and omits enough parameters (header, encoding, delimiter, verify_com, sheet) that an agent could not reliably construct a correct non-default call. The presence of an output schema does not offset these input-side gaps.

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 0%, so the description must compensate. It explains source/source_file, fmt auto-detection, location, formulas, allow_loss, and backup. However, it does not explain the required 'path' parameter at all, and it omits sheet, header, encoding, delimiter, and verify_com, leaving several parameters ambiguous for a non-default call.

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 opens with a specific verb and resource: 'Import CSV, TSV, or JSON into a sheet at an anchor.' It clearly conveys the tool's file-import purpose and formats. It does not explicitly distinguish itself from sibling write/export tools, but the format and anchor context make the distinction reasonably clear.

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 gives practical input-mode guidance (source vs source_file), anchor default, and several failure/refusal conditions. However, it does not explicitly state when to choose this tool over alternatives such as write_range, set_cells, or export_range; the usage context is implied rather than explicitly scoped.

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