connection_pool

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

With no annotations, the description carries the full burden. It clearly indicates a read-only monitoring operation and specifies the HikariCP-specific scope. However, it does not state safety guarantees, required permissions, or failure modes for non-HikariCP pools, so some behavioral context is still missing.

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, tightly packed sentence that lists the key responsibilities without filler or redundancy. It is front-loaded with the main action and scope.

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 simple one-parameter tool with no output schema, the description provides the core purpose but lacks parameter context, usage alternatives, and return details. The overlap with `connection_leak` and other siblings further limits how completely an agent can act on this description alone.

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 description coverage is 0%, and the tool description does not mention `database_name` at all. The parameter name is self-explanatory as a database identifier, but the description adds no semantic value about what the parameter controls or how it affects the monitoring scope.

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 clear verb ('Monitor') and resource ('HikariCP connection pool metrics') and lists specific outcomes: detect leaks and track wait times. It is distinct enough from most siblings but overlaps with `connection_leak`, which also focuses on leak detection, creating mild ambiguity.

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 such as `connection_leak` or `get_connections`. The description simply states what it does without mentioning when to choose it over a dedicated leak-detection tool or other monitoring tools.

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