fetchPostgreSQLSchema

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

No annotations are provided, so the description carries the full burden. It clearly indicates a read-only fetch ('Fetches the schema'), but does not disclose specifics like whether views, indexes, or constraints are included, or any permissions needed. Adequate but not detailed.

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?

A single sentence that is immediately clear, front-loaded with the verb, and contains no redundant words. Perfectly concise for its scope.

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?

No output schema exists, so the description must stand alone. It covers the primary purpose and output ('tables and columns') but could optionally mention return format or limitations. For a simple zero-parameter schema fetch, this is largely complete.

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?

Tool has zero parameters, so there is no parameter semantics to clarify. Baseline 4 applies per rubric guidance.

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 states a specific action ('Fetches the schema') with a clear resource ('connected PostgreSQL database') and what it returns ('showing tables and columns'). Distinguishes from sibling tools like executePostgreSQLSqlQuery (which runs queries) and fetchSupabaseSchema/fetchNeonSchema (other database engines).

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. Does not mention that it's for schema exploration before querying, nor does it exclude execution or other schema-fetching tools. The context signals sibling tools but the description alone gives no usage direction.

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