delete_statistics

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It explicitly states 'CAUTION: This is a destructive, irreversible operation', and it specifies the underlying SQL command (DROP STATISTICS) and the environment requirement (only on Data Warehouses). This fully informs the agent of the behavioral traits.

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 short, front-loaded with the essential action and caution, followed by a bullet-like parameter list with clear labels and examples. No redundant information is present; every sentence adds value.

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 tool has 4 required parameters and an output schema (not shown but present), the description fully explains all parameters and the operation's effect. It covers restrictions (Data Warehouses only), the destructive nature, and provides parameter examples. The presence of an output schema means return values need not be described. This is complete for an agent to use the tool correctly.

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%, meaning the input schema provides only titles with no descriptions. The description adds detailed explanations for each parameter: 'Workspace name or GUID', 'Warehouse name or GUID. SQL Analytics Endpoints are rejected', 'Qualified table name, e.g. ``dbo.sales``', and 'Name of the statistic to drop.' These significantly augment the schema and provide vital usage information.

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 that the tool drops a statistic via DROP STATISTICS, specifying the action and resource (statistic). It distinguishes from sibling tools like create_statistics and update_statistics by indicating this is a destructive, irreversible operation, and from read-only tools by restricting to Data Warehouses only.

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 provides guidance on when to use this tool: it is for dropping a statistic, and it warns against use on SQL Analytics Endpoints because they are read-only. However, it does not explicitly compare to alternatives like delete_table or other delete operations, but the context of 'statistics' and the caution make the usage clear.

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