search_columns

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

No annotations provided. The description adds the return format and example, but omits behavioral traits like read-only nature, case sensitivity, or potential performance impact. It provides basic transparency but no 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?

Three sentences covering purpose, example, and output. No redundant content, front-loaded with clear action and example.

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?

For a 2-parameter search tool with no output schema, the description sufficiently covers purpose, input, and output shape. Missing some contextual details like whether search is case-insensitive, but overall adequate.

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%. The description clarifies the 'keyword' parameter (column name or comment) and gives an example, but does not explain the 'limit' parameter beyond its default. Partial compensation.

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 it finds tables/views by column name or comment, with a concrete example. It differentiates from siblings like search_tables by focusing on columns.

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?

Usage is implied through the example but no explicit when-to-use or when-not-to-use guidance, nor alternatives mentioned. The description lacks directives for choosing this over search_tables or other tools.

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