Get Value Distribution

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

With no annotations, the description carries full burden. It discloses boundedness (topN), masking, and sample limits (rowLimit), which are key behavioral traits. However, it does not explain what masking does, how limits are enforced, or if there are side effects like data access restrictions. Lacks depth but covers core aspects.

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?

One sentence of 12 words, no fluff. Front-loaded with the key action and resource. Every part is meaningful, making it highly efficient for an agent to parse quickly.

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 six parameters, no output schema, and complex concepts like masking, the description is too brief. It does not explain the return format, interaction between topN and rowLimit, what 'allowed column' means (policy-driven?), or error scenarios. Leaves significant gaps for an agent to infer.

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?

Only 0% of schema parameters have descriptions. The tool description adds meaning by referencing 'bounded' (topN), 'sample limits' (rowLimit), and 'one allowed column' (column), but ignores parameters like schema and profile. It partially compensates for the lack of parameter descriptions but is insufficient for a full 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 the tool returns a bounded top-value distribution for one column, specifying the action (return) and resource (distribution for an allowed column). This distinguishes it from siblings like ob_profile_columns which profile multiple columns or ob_get_table_stats which provides 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 explicit guidance on when to use this tool versus alternatives. The description implies usage for value distribution queries but does not compare with siblings like ob_profile_columns or ob_describe_table, nor does it state prerequisites or constraints.

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