pg_execute_sql

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

The description discloses the blocking behavior when readOnly mode is enabled, but lacks details on rollback, error handling, or side effects. With no annotations, more transparency is needed.

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 two concise sentences, front-loaded with the core action, and contains no redundant information.

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 tool that executes arbitrary SQL with write/DDL capabilities, the description omits return format, error behavior, security considerations, and prerequisites beyond readOnly, making it incomplete for safe usage.

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 does not expand on the 'sql' parameter beyond what is in the schema, and the 'connectionId' parameter's description adds minimal value. Schema coverage is 50%, and the description does not compensate.

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 explicitly states the tool runs any SQL statement (INSERT/UPDATE/DELETE/DDL) against a Postgres connection, clearly distinguishing it from read-only siblings like pg_query.

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 mentions when to use (for write/DDL operations) and a key condition (blocked when readOnly is enabled), but does not explicitly direct users to pg_query for SELECT queries.

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