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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld=false, so the safety burden is light. The description adds genuine behavioral detail beyond them: newest-first ordering, the 24-hour default window, and the fact that filler (horoscopes, quizzes, gossip, promos) is silently excluded unless include_filler is set. Return shape is not described, but an output schema exists.

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?

Two sentences, both earning their place, with the resource description front-loaded before the urgent_only tip. The first sentence is quite dense with the coordinate/place/kind/reports enumeration, but nothing is redundant.

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?

With a full output schema and rich annotations, the description only needs to cover what those don't: default window, ordering, and the filler-exclusion behavior, all of which it does. The remaining gap is guidance on choosing this tool over the geo-adjacent siblings.

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%, so every parameter already carries its own explanation, and the description largely restates them (default 24 hours, urgent_only meaning). The one value-add is framing urgent_only as an 'emergency overview', but it does not clarify interaction between kinds and urgent_only or how limit interacts with the plan cap.

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?

States a specific resource and scope: every geolocated news story in the last N hours across Croatia and the world, newest first, with coordinates, place, kind and reports. That framing distinguishes it from get_latest_news, search_news and list_stories without naming them. It stops short of an explicit sibling callout, so a 4 rather than a 5.

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?

One concrete usage trigger is given: 'Use urgent_only=true for an emergency overview (fires, crashes, floods…)'. There is no guidance on when to prefer this over the nearest alternatives such as get_nearby_news or get_city_news, so the routing decision is only partly supported.

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