qlty_standardDeviation

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

No annotations are provided, so the description carries the full burden. It discloses the persist parameter's effect (materializing as a volatile table) but does not mention whether the tool is read-only or any side effects. The behavior is partially transparent but lacks completeness.

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: a single sentence of purpose followed by a bullet list of arguments. It is front-loaded and contains no unnecessary words or repetition. Every sentence is informative.

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 absence of an output schema and no annotations, the description should specify the return format. It explains the persist case but not the default return (likely a result set with mean and std dev). Otherwise, the essential information about what the tool does and its parameters is present.

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 100%, but the description adds minimal value beyond the schema. The argument list repeats schema descriptions, and only the persist parameter's behavior is explained in the description (matching schema). No additional meaning is provided for database_name, table_name, or column_name. The return value for the normal (non-persist) case is not described.

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 purpose: 'Get the mean and standard deviation for a column in a table.' The verb 'Get' and the specific resource 'mean and standard deviation' make it distinct from sibling tools like qlty_columnSummary or qlty_univariateStatistics.

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 only states the function without any context, exclusions, or comparisons to sibling tools, leaving the agent to infer usage from the purpose.

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