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

With no annotations provided, the description carries the full burden, and it does a solid job: it discloses the content scope, language behavior, and the exact fields returned per news item. It does not mention pagination, freshness guarantees beyond 'today', or error behavior, but for a straightforward news-reading tool the disclosed traits are sufficient.

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 compact sentences deliver the core purpose, the output item structure, and the language/scope caveats without wasted words. The most important information is front-loaded, and every clause adds useful guidance.

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?

Given the moderate complexity and lack of an output schema, the description adequately explains what the tool returns: title, summary, source, and link. It also covers the key behavioral nuances of language and local scope. It could be slightly more explicit that it returns a list and that edition values map to specific languages, but the schema and description together provide enough to call the tool correctly.

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 input schema already has 100% description coverage, so the baseline is 3. The description adds value by clarifying that the city parameter selects one specific city and that the edition parameter corresponds to the newsroom's own language. This helps an agent understand the relationship between city, edition, and the returned content beyond the schema's simple slug/key references.

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 clearly identifies the resource: today's local news for one city, including the per-item fields. It distinguishes from the sibling city_events by focusing on news rather than events, and from national wires via an explicit exclusion. It lacks an explicit verb like 'retrieve' or 'get', but the intent is unambiguous.

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?

The description gives clear context for when the tool is appropriate: local news published by the city portal itself, not national wires. It also sets expectations that the text is in the newsroom's own language. It does not explicitly name alternative sibling tools like city_events, so it stops short of a full when-to-use-versus-alternatives explanation.

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