MCP PostgreSQL Operations

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

With no annotations provided, the description carries full burden. It effectively communicates this is a monitoring/read-only tool (implied by 'Monitor', 'Show', 'Display', 'Provide') and specifies what information is returned. However, it doesn't mention potential limitations like data freshness, permission requirements, or rate limits.

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 uses clear section headers ([Tool Purpose], [Exact Functionality], etc.) to organize information efficiently. Every sentence adds value with no redundancy, and the structure helps the agent quickly understand purpose, functionality, usage guidelines, and returns.

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?

Given this is a monitoring tool with 0 parameters, 100% schema coverage, and an output schema exists, the description provides excellent context. It covers purpose, exact functionality, when to use, when not to use, and what's returned - making it complete for agent decision-making.

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 0 parameters with 100% schema description coverage, so the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on what the tool monitors and returns.

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 'Monitor PostgreSQL replication status and statistics' with specific functionality details like showing replication connections, lag information, WAL processes, and slot information. It clearly distinguishes this tool from sibling monitoring tools by focusing exclusively on replication aspects.

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 provides explicit 'Required Use Cases' (e.g., when user requests replication status, diagnosing issues) and 'Strictly Prohibited Use Cases' (e.g., configuration changes, slot creation/deletion, failover operations). This gives clear guidance on when to use this tool versus alternatives.

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