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

With no annotations, the description itself conveys only that this is a read-only 'get' operation. It discloses no further behavioral traits such as data freshness, units, caching, or failure behavior, though the simple getter nature makes this a modest rather than severe gap.

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 core message is a single actionable sentence with no filler. However, the empty '[COST: ]' prefix is a leftover placeholder that contributes no information and slightly weakens an otherwise concise definition.

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 read tool with an output schema, 'Get current weather in Berlin' covers the essentials. It could be more complete by noting freshness or units, but the output schema and explicit location make the tool callable without ambiguity.

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?

There are zero parameters, so there is nothing for the description to clarify beyond the schema. The baseline for a zero-parameter tool applies; the description adds no parameter semantics because none are needed.

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 verb and resource: 'Get current weather in Berlin'. It clearly identifies the geographic scope, distinguishing it from sibling weather tools such as get_london_weather and get_nyc_weather.

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 guidance is given about when to choose this tool over alternatives. The sibling list contains many weather tools, but the description does not mention selection criteria such as 'use for Berlin weather; use get_london_weather for London'.

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