List generated columns

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

Annotations already declare readOnlyHint=true. The description adds valuable behavioral context: explains the 'kind' field's purpose (forward compatibility), notes PG limitations, and details the exact output shape. No contradictions with annotations.

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 concise sentences with no wasted words. The first sentence front-loads the purpose and output fields, the second adds PG-specific context, and the third clarifies the response shape. 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?

Given the simple input (2 parameters, 1 required) and explicit output schema described in the description, the tool is fully specified. No missing details about return values or behavior; output schema is described in prose. No prerequisites or edge cases are needed for this straightforward listing tool.

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?

The description mentions the 'schema' parameter implicitly but does not describe the 'database' parameter at all. Schema description coverage is 50%, and the description adds minimal value beyond the input schema's own descriptions. The schema param context is clear, but the database param relies solely on the schema.

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 lists generated columns with specific fields (schema, table, column, data_type, expression, kind). It uses a specific verb ('List every ... STORED column') and resource, and distinguishes from sibling list_* tools by targeting a narrow subset of 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?

The description provides clear context about what the tool returns and notes that PostgreSQL only supports stored form, with forward compatibility. It does not explicitly state when not to use or name alternatives, but the specificity makes usage clear. Lacks explicit exclusion guidance.

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