Get Server Metrics

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true, indicating a safe, read-only operation. The description adds no further behavioral details such as rate limits, auth requirements, or error handling, but 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 a single sentence of about 15 words, front-loading the core verb and resource. Every word is necessary and conveys the tool's purpose without 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 no output schema, the description could provide more details about the return format (e.g., data points per metric). However, the parameter descriptions are clear, and annotations cover safety. The description is adequate but not fully complete for an agent to predict the response structure.

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?

All four parameters have detailed descriptions in the input schema (100% coverage), so the description adds minimal extra meaning. The phrase 'time series metrics (CPU, disk, network) over a time range' loosely references the 'type', 'start', and 'end' parameters but does not enhance understanding beyond the schema.

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 time series metrics (CPU, disk, network) for a server over a time range. It uses a specific verb ('Retrieve') and resource, effectively distinguishing it from sibling tools like hetzner_get_lb_metrics.

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 implicitly indicates usage for obtaining server metrics but lacks explicit guidance on when to use this tool versus alternatives (e.g., hetzner_get_server for static data or hetzner_get_lb_metrics for load balancers). No when-not or alternative tool mentions.

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