get_database_stats

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

The description mentions the source system views but does not disclose potential performance impact, staleness of data, or any prerequisites. Since no annotations are provided, the description carries full responsibility for behavioral disclosure, which it fails to satisfy.

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 sentence that directly states the tool's purpose without any extra words. It is concise and front-loaded.

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 the tool has no parameters, no output schema, and simple functionality, the description is minimally adequate. However, it could mention typical use cases or what the output contains (e.g., statistical counters) to be more 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?

There are no parameters, so the schema already covers 100% of the interface. The description does not need to add parameter semantics, and it correctly omits any. Baseline score of 4 is appropriate.

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 clearly identifies the tool as retrieving statistics about database activity and the background writer, naming the specific source views (pg_stat_database and pg_stat_bgwriter). This is distinct from sibling tools like get_database_connections which focus on connections.

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 provided on when to use this tool versus alternatives, nor any conditions or typical use cases. The description lacks contextual cues for an agent to decide if this is the appropriate tool.

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