show_statistics

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

No annotations are provided, but the description reveals it is a read-only operation via DBCC SHOW_STATISTICS. It clearly states what it returns, implying no side effects. More explicit confirmation of safety would be better.

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 well-structured: summary, return details, supported platforms, then parameter list. It is front-loaded and concise, though the Args list adds some length.

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?

Given the complexity and presence of an output schema, the description covers the purpose, parameters, and supported platforms adequately. It could mention prerequisites or permissions but is still complete enough.

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 coverage is 0%, but the description provides clear args with brief explanations and an example for qualified_table. This adds significant meaning beyond the schema's titles and types.

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 it shows details of a statistic using DBCC SHOW_STATISTICS and lists what is returned. It distinguishes from siblings like create_statistics, delete_statistics, and list_statistics.

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 mentions supported platforms but does not explicitly tell when to use this tool vs alternatives like list_statistics. It lacks guidance on when to use or avoid.

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