ecp_mssql_insert_row

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only states the basic mutation and does not mention that confirm=true is required, that database credentials are needed, what happens on constraint violations, or whether the operation is transactional. It is not misleading, but it is severely under-disclosing.

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 a single, front-loaded sentence with no filler. It is genuinely concise, though the brevity contributes to under-specification in other dimensions.

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?

This is a credentialed write operation with a nested values object, a required confirm flag, and no output schema or annotations. The description does not cover confirmation semantics, values shape, or prerequisites, so it is not complete enough for an agent to invoke reliably.

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% and the description adds no parameter meaning. It does not explain the structure of the values object, why confirm must be true, or how db_name, table_name, db_username, and password are used. The description fails to compensate for the undocumented parameters.

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 states a clear action and object: 'Insert a row into a table.' However, it does not distinguish this tool from siblings like ecp_mysql_insert_row or ecp_postgres_insert_row, leaving engine and operation differentiation entirely to the tool name.

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?

There is no guidance on when to use this tool versus alternatives such as update_row, delete_row, or browse_rows. It also omits prerequisites like table existence or the mandatory confirmation flag, so an agent receives no contextual decision help.

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