health_check

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

Annotations already declare readOnlyHint=true and no destructiveness, so the safety profile is clear. The description adds value by specifying what is checked (availability, engine version, storage health), which is beyond the annotations. It does not contradict annotations.

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 two concise sentences, front-loading the key purpose and ending with a helpful qualifier ('Public method'). Every word earns its place with no redundancy.

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 zero parameters and the presence of an output schema, the description is complete for its simplicity. It covers the key checks performed, though it doesn't elaborate on return values (covered by output schema) or error cases. Adequate given the low complexity.

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 input schema has no parameters, so the description has nothing to add beyond specifying the general purpose. Baseline 3 is appropriate because the schema coverage is 100% and no parameter details are needed.

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 checks 'service availability, engine version, and storage health'. It uses a specific verb ('check') and resource ('service', 'engine', 'storage'), and the 'Public method' addition distinguishes it from tools that might require authentication or have restricted access.

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 provides clear context that this is a health check tool, but there is no explicit guidance on when to use it versus other tools (e.g., when to use health_check vs. slo_report). However, the context is sufficient for most scenarios given its broad nature and zero parameters.

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