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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety and external-data sourcing are covered. The description adds one genuinely useful behavioral fact — the data is scoped to "today" — but says nothing about the shape of the single opaque "input" argument, freshness/latency, or whether results are partial.

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?

One front-loaded sentence with the resource first and the returned fields after the colon; nothing is padded or repeated. It is arguably too terse, but that is a completeness problem rather than a structure problem.

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, no annotation detail on returns, and one fully undocumented parameter mean the description has to carry the load and doesn't. An agent cannot construct a valid call from this text.

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 0% and the single required parameter is literally an untyped `{}` named "input". With the schema contributing nothing, the description must explain what goes in that argument, and it does not — no hint about whether it is a place, a station id, a bounding box, or a time window.

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?

"Radiosondes heard today" names a specific resource and enumerates the payload fields (height, speed, climb), so the agent knows roughly what comes back. But it never distinguishes this tool from the sibling cell_sensor_sondes, and the meaning of the "_at" suffix (a snapshot at a point in time, presumably) is left to be inferred from the name alone.

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?

There is no statement of when to use this versus cell_sensor_sondes or the many other cell_sensor_*_at siblings. The only implied usage cue is "today", which hints at a recency window but doesn't say what to do for other time ranges or which sibling covers them.

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