Get Table Data (deprecated — use mssql_read_table_rows)

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

Annotations already provide readOnlyHint and idempotentHint, so the description's deprecation notice and the @paramName placeholder requirement add valuable behavioral context beyond the structured data. No contradiction with annotations.

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 concise: two sentences that front-load the deprecation status and directive to use the alternative. The warning is included without excess words.

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 fully serves the primary purpose of redirecting agents to the proper tool. However, since there is no output schema and no info about return format or the remaining parameters, it is not sufficient for direct invocation if someone bypasses the deprecation warning.

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%, so the description must compensate. It only explains the whereClause placeholder requirement, leaving the other 7 parameters (limit, offset, orderBy, tableName, parameters, schemaName, response_format) without any additional meaning.

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 this is a deprecated alias for mssql_read_table_rows, and the title 'Get Table Data' implies its function. It distinguishes itself from siblings by explicitly naming the replacement tool, though it doesn't elaborate on what the underlying operation does.

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?

It explicitly instructs to use mssql_read_table_rows instead, providing unambiguous when-to-use guidance. It also adds a critical usage warning about whereClause requiring @paramName placeholders, which is directly actionable for correct invocation.

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