fetchPostgreSQLSchema

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

There are no annotations, so the description must fully disclose behavior. It mentions the action and output but does not state whether the operation is read-only, whether it requires special permissions, or what specific schema objects are included (e.g., views, indexes, all schemas). This is minimal behavioral transparency.

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, clear sentence with no redundant words. It is appropriately front-loaded with the verb and object, making it easy to scan.

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?

For a zero-parameter tool, the definition is fairly complete, but it lacks details about the return structure beyond 'tables and columns', and there is no output schema to clarify. It may leave the agent uncertain about whether other database objects are included.

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 tool has zero parameters, and the description correctly does not address parameters. The baseline for zero-parameter tools is 4, and the description adds no confusion or unnecessary parameter detail.

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 a specific verb 'Fetches' and a clear resource 'schema of the connected PostgreSQL database'. It distinguishes itself from sibling schema tools like fetchSupabaseSchema and fetchNeonSchema by specifying the generic PostgreSQL database, and from executePostgreSQLSqlQuery by focusing on schema rather than arbitrary SQL.

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 given on when to use this tool versus alternatives such as fetchSupabaseSchema or fetchNeonSchema, or whether to use executePostgreSQLSqlQuery instead. The description only states what it does, not when to prefer it.

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