get_connection_pool_status

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

With no annotations provided, the description bears the full burden of behavioral disclosure. It labels itself a '[probe]', suggesting a read-only operation, but does not state whether it requires special permissions, is expensive, or what the response shape is. It lists metrics but lacks details on side effects or limitations, leaving the agent to infer safety.

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, efficient sentence that front-loads the key metrics. The additional note about pool exhaustion being a common cause adds diagnostic context without being verbose. It is appropriately concise and structured, though the second clause could be seen as slightly optional.

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 probe with three optional parameters and no output schema, the description is mostly sufficient. However, it does not explain how the parameters interact (e.g., whether pod or service is preferred) or describe the return format. Given the absence of an output schema and annotations, more detail on expected response structure would improve completeness. It is adequate but has clear gaps.

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 100%, so all three parameters (pod, service, namespace) have individual descriptions. The tool description does not add any additional parameter context beyond what the schema already provides. It does not clarify when to use 'pod' versus 'service', but the schema descriptions themselves are adequate. Baseline 3 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 states the tool retrieves HikariCP connection pool metrics (active/idle/pending/max, acquire/usage times, timeouts), making its purpose evident. It distinguishes from generic health tools by focusing on the connection pool, though it doesn't explicitly name alternatives. The verb is implicit but the resource and metrics are specific.

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 note 'Pool exhaustion is the #1 Java+DB slowness cause' implies this tool is for diagnosing DB slowness, providing some context. However, it does not explicitly state when to use this tool versus alternatives like get_jvm_health or diagnose_slow_requests, nor does it mention exclusions. The guidance is implied rather than explicit.

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