mssql_execute_sql

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

With no annotations, the description carries the behavioral disclosure burden and does reveal key behavior: arbitrary SQL execution, GO batch splitting, optional parameters, and transaction support. However, it does not mention potential destructive side effects, result/return behavior, or permission requirements, so transparency is partial.

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 compact and well-structured: one clear declarative sentence followed by two illustrative examples. There is no filler, and the core behavior is front-loaded.

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 schema covers all parameters and the description covers invocation patterns and transaction behavior, which is adequate for basic use. However, there is no output schema, and the description does not state what the tool returns (rows, affected counts, etc.), leaving a notable gap for a generic SQL executor.

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 schema already documents all six parameters. The description adds only a high-level mention of optional parameters and a transactional example, providing no additional meaning beyond what the input schema already states.

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 executes arbitrary T-SQL, with examples spanning DDL (CREATE INDEX) and a CTE SELECT, so its generic scope is evident. However, it does not explicitly contrast itself with siblings like mssql_execute_query or mssql_execute_mutation, leaving some boundary inference to the agent.

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 phrase 'arbitrary T-SQL' and the examples imply this is the general-purpose runner, but the description never states when to prefer it over the specialized sibling tools or when not to use it. No exclusions or alternative routing guidance is provided.

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