Execute Query (deprecated — use mssql_run_sql_query)

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

The description adds a warning that the tool can read and modify data, complementing the readOnlyHint=false annotation. It also discloses the deprecated status, which is not present in annotations. However, it does not detail other behavioral aspects like authentication or side effects, though the deprecation reduces the need.

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?

Two short sentences plus a warning icon, front-loaded with deprecation and the alternative. Every word earns its place, and the structure is immediately scannable.

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 deprecated tool, the description provides essential guidance: what it is, what to use instead, and a safety warning. It lacks details about return values or specific usage scenarios, but these are less critical given the deprecation and the explicit pointer to the replacement.

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?

The description does not discuss parameters. The input schema documents 'query' and 'parameters', but 'response_format' only has an enum without a description. With 67% schema coverage, the description adds no additional semantic value, leaving some parameter meaning unclear.

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 identifies the tool as a deprecated alias for mssql_run_sql_query, making its function apparent through reference. The title reinforces 'Execute Query'. It distinguishes from siblings by pointing to the preferred alternative.

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?

Explicitly instructs to use mssql_run_sql_query instead, providing clear when-not-to-use guidance. This is exactly the kind of direct alternative direction that helps an agent decide correctly.

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