Find Computed Columns

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

With no annotations, the description must fully disclose behavior. It states 'list' implying read-only, but does not explicitly confirm no side effects, required permissions, or output format. Key behavioral traits like whether it queries the database or returns cached results are absent.

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 concise sentence with no redundant words. It directly states the action and purpose, fitting within the context of sibling tools. However, it could be slightly more structured with separation of usage hints.

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 no output schema, the description hints at return values (columns and formulas) but lacks specifics like data types or pagination. The tool has 3 optional parameters, and the description does not address how outputs are organized. It is minimally adequate but not fully self-contained.

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?

All three parameters have descriptions in the schema (100% coverage), so the description's contribution is minimal. It adds no extra meaning beyond the schema, such as explaining the role of connectionName or clarifying the default schema behavior. Baseline 3 is appropriate as the schema carries the load.

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 the specific verb 'List' and clearly targets resource 'computed columns' with purpose 'to understand derived business logic'. It effectively distinguishes from sibling tools like list_tables or list_indexes by focusing on computed columns, though it does not explicitly differentiate from similar schema analysis tools.

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 is provided on when to use this tool versus alternatives, such as analyze_table_stats or describe_table. There is no mention of prerequisites, limitations, or when not to use it. The usage context is only implied by the purpose statement.

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