Get health observations

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. The description adds the notion of normalization and the requirement to resolve the full definition, which provides some context about behavior. No contradiction found, but no additional details on rate limits, pagination, or response characteristics.

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 with no redundant words. It is front-loaded with the core function, but the second clause is somewhat cryptic, reducing clarity slightly.

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?

The description is too minimal for a tool with 9 optional parameters. It does not explain the relationship with search_indicators (which supplies indicator_id and rate_type), nor does it mention any prerequisites or typical usage scenarios. The output schema covers return values, but usage context is missing.

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 description coverage is 100%, so every parameter has an individual description. The tool description adds no parameter-level information beyond what the schema provides, keeping this at baseline.

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 says 'Return a normalised series', which gives a specific verb and resource. It distinguishes from sibling get_latest_observation (which returns a single observation) by explicitly returning a series. However, the phrase 'only after resolving its full definition' is vague about what that 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 explicit when-to-use or alternative tool guidance. The phrase 'only after resolving its full definition' hints that some prerequisite must be met but does not explain how or when to use this tool vs search_indicators. Missing clear exclusions or alternatives.

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