qlty_distinctCategories

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

Annotations indicate readOnlyHint=true and idempotentHint=true. The description is consistent and adds context: explains that setting persist=True materializes a volatile table and returns the table name, which is significant behavioral information beyond the annotations.

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 very concise: three sentences cover purpose, usage condition, and parameters. It is front-loaded with the main action, and each part serves a clear purpose. No unnecessary words.

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 is straightforward (retrieving distinct values) and has no output schema, the description covers purpose, usage, parameters, and a special condition (missing column). It could mention limitations like performance on large columns, but overall it is complete for the tool's complexity.

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%, so baseline is 3. The description adds usage semantics beyond the schema by stating that column_name must be specified and if missing, ask for clarification. Also explains the effect of persist parameter, which adds value over the schema description.

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 retrieves unique values from a column, with specific verb 'Get the unique (distinct) values'. It distinguishes from sibling tools like qlty_columnSummary by specifying the exact use case (unique values/categories) and providing usage guidance.

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?

Explicitly states when to use: 'when the user asks what unique values, categories, or entries exist in a named column'. Provides action for missing column: 'ask for clarification before calling'. However, does not mention when not to use or alternatives, so not a perfect 5.

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