get_news_by_location

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

Annotations already mark it readOnly and non-destructive, so the safety profile is covered. The description adds that it returns recent articles filtered by geography, but does not disclose behavior like result limits, period handling, or the relationship between full_data and summarize, though the schema documents these.

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 short sentences with no filler. The core action and scope are front-loaded, followed immediately by routing guidance to an alternative tool.

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 complete input schema, output schema, and read-only annotations, the description covers the essential call context. It names the intended use case and the key alternative, though it leaves parameter interplay details to the schema rather than adding its own guidance.

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 the schema fully documents all five parameters. The description's mention of 'city, state, or country' reinforces the location parameter but adds little beyond the schema's existing 'Name of city/state/country' text.

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 ('Find') and resource ('recent Google News articles'), scoped to 'place-focused location such as a city, state, or country.' It also distinguishes itself from get_news_by_keyword, making the tool's purpose 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?

It explicitly says to use this tool 'when geography is the primary filter' and directs users to get_news_by_keyword for 'general subject searches.' This gives clear selection criteria relative to at least one sibling and implies location-specific usage.

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