hcloud_list_health_monitors

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

No annotations are provided, so the description must bear the full burden of behavioral disclosure. It fails to mention that this is a read-only operation, any permissions required, pagination behavior, or response format. The bare statement 'List ELB health monitors' is insufficient for an agent to understand side effects or limits.

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 sentence, directly stating the action. It is front-loaded and concise with no wasted words. While it could include more details, it earns its place for brevity.

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 list tool with two parameters and no output schema, the description is barely adequate. It lacks context about what a health monitor is, its relationship to load balancers, and what the returned data looks like. More completeness would help an agent understand the tool's role.

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 descriptions already cover both parameters (region, limit) fully. The tool description adds no additional parameter context beyond the resource name. Per the guidelines, with 100% schema coverage, baseline is 3.

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 'List ELB health monitors' clearly states the verb and resource. It is specific to ELB health monitors, which distinguishes it from sibling list tools like hcloud_list_load_balancers. However, it does not explicitly differentiate from alternatives, so a score of 4 is appropriate.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, filters, or exclusions. Without this, an agent may struggle to choose the correct tool among many list tools.

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