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

With no annotations provided, the description bears the full burden of behavioral disclosure. It adds one useful behavioral detail—the default time window of the last 7 days—but omits other important behavior such as return format, ordering, timezone handling, pagination, or how limit interacts with the time range.

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 concise sentence that front-loads the core purpose and includes the key default behavior. It is not bloated, though it could be slightly more informative without becoming verbose.

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 5 parameters, no output schema, no annotations, and several sibling tools, this description is too sparse. It does not explain what the tool returns, how defaulting works for from/to in detail, or how this differs clearly from get_latest_metrics. An agent would need additional inference or external knowledge to use it confidently.

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 already documents all parameters with 100% coverage, so the baseline is 3. The description adds no additional parameter-specific meaning beyond implying that from/to relate to a time range, which the schema already conveys.

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 identifies the resource: the time series of measurement values for a specific instance. 'Zeitverlauf' (time course/history) distinguishes this from the sibling get_latest_metrics, though no explicit verb like 'retrieves' or 'returns' is used.

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 implies this tool is for historical metrics by saying 'Zeitverlauf' and noting the default of the last 7 days. However, it does not explicitly state when to use this tool instead of get_latest_metrics, nor does it mention any exclusions or alternatives.

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