Profile Table Columns

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

The description mentions 'policy-filtered' and 'allowed' table, implying authorization and filtering, but does not disclose specifics like read-only nature, rate limits, or what 'bounded' entails. Without annotations, the description partially addresses behavior but lacks depth.

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 a single sentence, which is concise, but it omits critical details, making it under-specified. It is front-loaded but does not earn its place by being sufficiently 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 complexity (8 parameters, no output schema, no annotations), the description is severely incomplete. It fails to explain what a column profile is, how policies filter, or how parameters influence results, leaving the agent without sufficient information.

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?

With 0% schema description coverage and 8 parameters, the description adds no information about any parameter. It fails to explain what parameters like 'columns', 'profile', or 'rowLimit' mean or how they affect the output.

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 'column profiles' with qualifiers 'bounded' and 'policy-filtered', which distinguishes it from sibling tools like ob_describe_table or ob_get_table_stats. However, the term 'profile' is not defined, leaving some ambiguity.

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 offers no guidance on when to use this tool versus alternatives such as ob_describe_table or ob_sample_rows. No context is provided for appropriate use cases.

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