qlty_standardDeviation

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

The description only mentions the behavioral effect of the 'persist' parameter (materializing as a volatile table). It does not state whether the tool is read-only, any side effects, required permissions, or performance implications. With no annotations, this is insufficient.

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 with two sentences and a bullet list. It is well-structured but contains some redundancy as it duplicates schema descriptions. No unnecessary sentences, but could be more succinct.

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?

The description lacks essential context such as the return format (what is returned besides the table name when persisted?), data type requirements for the column, and error conditions. With no output schema and minimal behavioral info, completeness is low.

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 description simply restates the schema's parameter descriptions. It adds no new semantic information beyond what the schema already provides, meeting the baseline of 3.

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 the tool's function: getting mean and standard deviation for a column. The verb 'get' and resource 'column' are specific. However, it does not explicitly distinguish from siblings like qlty_columnSummary or qlty_univariateStatistics, which also compute 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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when not to use it, or how it compares to siblings. The agent is left without context for selection.

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