Find Columns

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It does not explain what 'visible' means, whether there are auth requirements, rate limits, or any side effects. The tool has 7 parameters but no behavioral context beyond the search criteria.

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 of 15 words, front-loading the purpose. Every word is functional with no fluff. It is appropriately sized for a read-only search tool.

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 7 parameters, 0% schema coverage, no annotations, and no output schema, the description is grossly insufficient. It does not explain return values, pagination, or how to combine parameters. For a tool with 57 siblings, more context is needed to help the agent select and invoke correctly.

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 0%, so the description must compensate. It mentions 5 search criteria but does not align them clearly with the 7 parameters. For example, 'name' corresponds to 'query', but this is implicit. Parameters like 'limit', 'schema', 'profile' are not explained. The description adds some mapping but is incomplete.

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 uses a specific verb 'find' and resource 'visible columns' with multiple search criteria (name, comment, data type, table pattern, business term). It clearly distinguishes from sibling tools like ob_describe_table or ob_find_tables_by_business_term by focusing on columns across tables.

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 implies usage for searching columns by various attributes but provides no explicit guidance on when to use this tool vs alternatives like ob_search_catalog or ob_describe_table. No exclusions or context provided.

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