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

With no annotations, the description carries the full behavioral burden and delivers almost none of it. It does not disclose units (metric/imperial), data source, freshness/latency, rate limits, or error behavior for unknown cities, all of which matter for a live weather lookup.

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?

A single four-word phrase with zero filler and the scope qualifier ('Current') front-loaded. It is efficient, though its extreme terseness sits close to under-specification rather than model conciseness.

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 tool is simple (one required param, no nested objects, no output schema), so the description is minimally adequate. However, with no annotations and no output schema, nothing tells the agent what the response looks like or in what units, leaving a real gap.

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% and the single 'city' parameter is documented with an example ('London'), so the schema does the heavy lifting. The description only adds 'any city', which conveys no format or disambiguation guidance 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 gives a specific verb+resource ('get... weather') and narrows scope with 'Current' and 'any city', which implicitly separates it from the sibling get_forecast. It stops short of naming or explicitly contrasting that sibling, so it is clear but not fully differentiated.

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?

Usage is only implied: 'Current' suggests now-conditions rather than a forecast, which is the natural contrast with get_forecast. No explicit when-to-use statement, exclusions, or named alternative is provided, so an agent must infer the routing.

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