qlty_columnSummary

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

No annotations provided. Description only explains the persist parameter but does not disclose any behavioral traits like performance implications, auth requirements, or how large tables are handled.

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 and front-loaded with the purpose. However, listing all parameter details duplicates the schema, which could be omitted to improve conciseness.

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?

Describes the tool's main function and the persist option. Lacks details on the return format (e.g., which statistics are included) and does not address edge cases like empty tables.

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% with all parameters described. The description repeats the parameter descriptions without adding new meaning, so it meets the baseline but does not enhance understanding.

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 'Get column summary statistics for all columns in a table', which is a specific verb+resource. It distinguishes from sibling tools like qlty_distinctCategories or qlty_missingValues that focus on specific 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?

No guidance on when to use this tool vs alternatives. Siblings include many column analysis tools, but description does not specify scenarios or exclusions.

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