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

With no annotations, the description carries full behavioral burden and does well: it guarantees provenance, distance, age, measured/predicted status, confidence, and source divergence reporting, and states that unavailable required evidence is named rather than estimated. This is substantial transparency for a read-style retrieval tool.

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?

Three dense sentences front-load the core purpose and then expand with high-value behavioral guarantees. No filler words; every sentence contributes.

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?

No output schema exists, so the description must communicate return semantics, and it does by enumerating the preserved attributes and the missing-evidence policy. It could be more complete by specifying response format or units, but the essential contract for a caller is present.

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 conceptual context by framing lat/lng as a 'coordinate' and mentioning historical reliability, which lightly relates to the time parameter, but it adds no parameter-level syntax 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 opens with a specific verb ('Return') and a precise object: current physical-world evidence and historical forecast reliability for a coordinate. This makes the core function clear. It does not explicitly distinguish itself from get_forecast_trust, but the evidence-focused wording separates it from list_domains and check_operability.

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 the tool is for obtaining coordinate-bound evidence and reliability data, but it never states when to prefer it over the sibling tools or when not to use it. No exclusions or alternative routing are provided, so the agent must infer usage from the purpose statement.

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