get_pool_stats

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

No annotations are present, so the description must fully disclose behavior. It only says 'get' which implies a read operation, but does not specify whether it is side-effect-free, what kind of statistics are returned, or any requirements (e.g., active connection). Without annotation, this is insufficient for an agent to gauge safety and expected results.

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?

A single concise sentence that directly states the tool's verb and target. No fluff or redundant phrasing, and the key information is 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?

There is no output schema or annotations, so the description must convey what the function returns and any relevant context. It only states 'connection pool statistics' without elaborating on the specific metrics, format, or any prerequisites, leaving the agent under-informed for a stats-retrieval tool.

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 schema already provides 100% coverage of the single parameter (connectionId) with a clear description. The description adds nothing beyond that, so the baseline of 3 applies.

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 specific verb ('Get') and a clear resource ('connection pool statistics') with a scope ('for a connection'). It distinguishes from siblings like get_database_stats (which likely returns overall stats) and get_connection_info (which returns metadata, not pool statistics).

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 implies that this tool is used when you need per-connection pool statistics, but it does not explicitly state when to use it over alternatives such as get_database_stats or get_connection_info. No exclusions or alternative guidance is provided.

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