db_postgres_query

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

With no annotations, description carries full burden. Only declares 'read-only' (safe), but does not disclose other behavioral traits like return format, error handling, rate limits, or that the query is executed as-is without escaping. Minimal 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?

Single sentence is concise, but the brevity sacrifices necessary detail. Front-loaded with 'SAFE' label, but overall structure fails to cover critical information about parameters and usage.

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, no annotations, and two parameters with zero description. For a tool that executes SQL queries, the description is far from complete, missing parameter semantics, result expectations, and potential risks.

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 coverage is 0%, yet description provides no information about parameters. Does not explain what 'query' string should contain (e.g., SQL syntax) or what 'params' array is for (e.g., parameterized queries). Zero semantic value beyond 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?

Description explicitly states 'Execute a read-only PostgreSQL query', specifying the action (execute), the resource (PostgreSQL query), and constraint (read-only). Clearly distinguishes from sibling tools like db_mysql_query or db_mongodb_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?

No explicit guidance on when to use this tool versus alternatives. Does not mention that read-only queries should go here while mutation queries or health checks have separate tools. Implied by 'read-only' but not stated.

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