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

With no annotations, the description carries the full burden. It usefully discloses that no bundled condition claims are returned and that certain widgets are retired, which sets expectations. It still leaves unclear what exactly is returned (e.g., URLs, text, timestamps format) and whether the tool performs live network lookups.

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 three sentences and front-loads the main purpose before the negative and deprecation notes. It is efficient, though 'weather reader' is slightly jargon-like and the Queenstown specificity could be clearer.

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?

For a zero-parameter tool without an output schema, the description should clarify the return shape. It names the kinds of outputs (reader, timestamps, links) but does not specify format or structure, leaving an agent unsure what invoking it actually yields.

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 tool has zero parameters, so there is no parameter meaning to add beyond the empty schema. The baseline for a no-parameter tool is 4.

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 states a specific action (find the Queenstown weather reader and source timestamps) plus official travel and resort report links. It distinguishes itself from travel-planning siblings by being a source locator rather than a trip planner. The name 'live_conditions' could imply returned conditions, but the description explicitly corrects that expectation.

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?

It implies usage by stating what it does not return (current condition claims from bundled data) and that road/ski widgets are retired. However, it does not explicitly say when to use this tool versus a sibling or what alternative to use when actual condition data is needed.

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