mssql_execute_query

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

With no annotations, the description must carry behavioral transparency. It does disclose that the tool can execute mutating statements (INSERT, UPDATE, DELETE, EXEC), signaling side-effect risk. However, it does not mention transaction/commit behavior, result-set return, or whether DDL statements are supported.

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 concise sentence that front-loads the verb and resource, then immediately lists relevant query types. No filler or redundant content.

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 two-parameter tool this is minimal but workable: the agent knows what query to pass and can name a database. Missing output schema and annotations leave questions about result format and side-effect/commit behavior unanswered, so it is not fully complete.

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% for both query and database, so the schema already explains the parameters. The description adds no extra meaning about parameter format, defaults, or the behavior of the optional database parameter.

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 a specific verb and resource: 'Execute a T-SQL query' on the MS SQL database, and enumerates supported statement types (SELECT, INSERT, UPDATE, DELETE, EXEC). This clearly distinguishes it from sibling metadata tools such as mssql_list_tables and mssql_describe_table.

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 implies this is the general-purpose query execution tool, but it never explicitly says when to prefer it over siblings or when not to use it. No exclusions or alternative routing are provided; usage context must be inferred from the sibling tool names.

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