overview

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

No annotations present, so description carries full burden. It explicitly marks the tool as '[READ]' and notes defensive capture behavior ('each section captured defensively so one failing probe does not sink the rest'), adding useful context beyond a simple read hint.

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?

Headline clearly states purpose, bullet points list captured metrics efficiently, and parameter description is direct. No extraneous words; each sentence adds value.

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?

Lacks output schema but provides a comprehensive list of captured metrics, giving the agent a solid understanding of what to expect. Could benefit from a note on response format or error handling, but adequate for a health snapshot 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?

Single parameter 'target' has schema coverage 0%, but the description adds meaningful context: 'Target name from config; omit for the default.' This clarifies its purpose and default behavior.

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?

Clearly states it's a '[READ] One-shot cluster health snapshot' and lists specific metrics (version, uptime, connections by state, etc.). This differentiates it from sibling tools like list_activity or long_running_queries which focus on specific 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?

Implies use for quick health check via the bullet points, but does not explicitly describe when to use vs. sibling tools or when not to use it. Provides basic guidance on the 'target' parameter but lacks broader context.

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