db_columns

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

Description confirms read-only nature and mentions pg_catalog, but adds little beyond annotations which already include readOnlyHint, idempotentHint, and openWorldHint. No additional behavioral traits disclosed.

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?

Single sentence, front-loaded with key purpose information. No fluff, every word 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?

With 4 undocumented parameters and many sibling tools, the description is insufficient for an agent to correctly select and invoke the tool. Output schema exists but does not mitigate parameter gaps.

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% and description provides no information about parameters (projectId, projectRef, table, schema). The description does not compensate for missing schema descriptions.

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 read-only tool for inspecting columns and primary-key details via pg_catalog, using specific verbs and differentiating from sibling tools like db_table_schema and db_fk.

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?

Description implies use for column questions but does not explicitly state when to use versus alternatives or provide exclusions. It lacks concrete guidance on context.

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