qlty_univariateStatistics

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

No annotations provided, so description carries burden. It mentions the persist parameter that materializes results, hinting at behavior. However, it omits whether the operation is read-only, required permissions, or what 'full univariate statistics' includes.

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?

Description is short but includes a redundant list of arguments already in the schema. Could be more concise by omitting repetition, but it is not excessively long.

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?

No output schema provided, yet description does not clarify what statistics are returned (e.g., count, mean, std). Missing return value details and edge cases (null handling, empty tables). Persist behavior is described but insufficient overall.

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%, and the tool description repeats parameter descriptions verbatim, adding no extra meaning. Baseline 3 is appropriate as no enrichment beyond schema.

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?

Description explicitly states the verb 'Get' and resource 'full univariate statistics for a column', providing clear purpose. It distinguishes from sibling tools like qlty_columnSummary or qlty_standardDeviation which are more specific.

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?

No guidance on when to use this tool versus alternatives like qlty_columnSummary or qlty_standardDeviation. The description only explains what it does, not when it is appropriate.

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