qlty_missingValues

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

Annotations already declare readOnlyHint=true and idempotentHint=true; description aligns and adds context: returns a column-level summary, and persist parameter materializes a volatile table. Adds value beyond 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?

Description is concise and well-structured with a usage paragraph and argument list. Slight redundancy between first two sentences ('list column names' vs 'column-level summary'). Still efficient.

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; description says 'column-level summary' but doesn't specify if it includes counts or just names. However, it explicitly distinguishes from qlty_rowsWithMissingValues, and the persist parameter behavior is explained. Adequate for a simple analysis tool.

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%, so baseline 3 is appropriate. Description repeats parameter info but adds minimal extra context (e.g., 'Name of the database (optional)'). No significant improvement over 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 clearly states the tool lists column names with NULL/missing values, specifying verb (list) and resource (columns in a table). Explicitly distinguishes from sibling qlty_rowsWithMissingValues.

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?

Provides explicit usage: 'Use when the user asks which columns have nulls...' and 'Do NOT use to retrieve actual data rows — use qlty_rowsWithMissingValues'. Clear when-to-use and when-not-to-use with alternative tool named.

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