hcloud_show_metric_data

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the basic function. It does not describe the output format, pagination, rate limits, or any side effects. The schema covers parameter semantics but not behavior. This is insufficient transparency for a tool with 8 required parameters.

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, which is concise and front-loaded. It efficiently conveys the basic purpose. However, it could be restructured to include key usage tips without significantly increasing length.

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 the complexity (8 required params, no output schema, no annotations), the description is too sparse. It does not explain what the output looks like (e.g., array of data points, timestamps, values) or how to interpret the result. The tool's purpose is clear but the description is incomplete for effective use.

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 coverage is 100%, so the baseline is 3. The description adds no additional parameter information beyond what the schema provides. While the schema is comprehensive, the description does not enhance understanding of parameters like 'dim_0' or 'filter' beyond their descriptions.

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 'Show CES (Cloud Eye) metric data points' clearly states the action (show) and resource (metric data points). It distinguishes from siblings like 'hcloud_list_metrics' which lists available metric names, not data points. However, 'CES' is an acronym that may not be universally understood, and the description could be more specific about what 'metric data points' entails.

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?

No guidance is provided on when to use this tool versus alternatives. For instance, it does not mention that one might first call 'hcloud_list_metrics' to find valid metric names, or that this tool retrieves historical time-series data. The description lacks any usage context.

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