mssql_import_table_data

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

With no annotations present, the description carries the full burden of behavioral disclosure. It only says 'Import data', which hints at a write operation, but it does't disclose that the table may be truncated first, that inserts are batched, that a connection string may be required, or that the operation is transactional. These meaningful behaviors are left to the schema or entirely undisclosed.

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?

A single, front-loaded, waste-free sentence conveys the essential operation. There is no repetition of schema details, no filler, and the key semantic elements (import, format, file, table) appear in the expected order.

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 tool with 8 parameters, no output schema, no annotations, and many sibling tools, the description is underspecified. It does not clarify whether this is a mutating operation beyond the word 'import', when truncateFirst would be relevant, how connection strings are resolved, or what failure modes exist (e.g., file not accessible, schema mismatch).

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 75%, so most parameters are already explained in the input schema. The description reinforces that the file is JSON/CSV and the target is a table, but it adds no new meaning for batching, delimiter, truncation, or connection string semantics. The two bare schema parameters (format and batchSize) receive no help from the description either.

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 names the action (Import), the source data type (JSON or CSV file), and the target (table), making the core purpose clear. It is semantically distinct from the obvious sibling mssql_export_table_data, but it doesn't explicitly call out the difference from generic mutation tools such as mssql_execute_mutation.

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 no guidance about when to choose this tool over alternatives like mssql_execute_mutation or mssql_execute_sql, nor does it mention prerequisites such as accessible file paths or connection string requirements. Usage is only vaguely implied by the word 'Import'.

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