get_all_column_references

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

With no annotations, description provides return format and mentions errors, but lacks details on side effects, performance, or prerequisites. It does note the dialect parameter influences behavior.

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?

Extremely concise with clear structure: purpose sentence followed by structured Args and Returns. No unnecessary text, every sentence earns its place.

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?

Tool is simple with 2 parameters and no output schema. Description covers purpose, inputs, and output type. Lacks example output but sufficient for basic understanding.

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%, but description adds meaning: 'sql: SQL statement to analyze' and 'dialect: Optional SQL dialect (e.g., 'mysql', 'postgres')', including an example for dialect.

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 'Extract column references from SQL statement with table context', which is a specific verb and resource. It implicitly distinguishes from sibling 'get_all_table_references' by focusing on columns, but does not explicitly contrast.

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 guidance on when to use this tool versus alternatives (e.g., get_all_table_references, lint_sql). Only states its purpose, not when-not or context.

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