Google News13 MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool 'gets sport news' but doesn't reveal any behavioral traits such as rate limits, authentication needs, data freshness, pagination, or error handling. For a read operation with no annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 description is a single, clear sentence with zero wasted words. It's front-loaded with the core purpose ('get sport news'), making it easy to parse. Every element earns its place by directly stating what the tool does.

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 lack of annotations and output schema, the description is incomplete. It doesn't address key contextual aspects like what format the news is returned in (e.g., headlines, full articles, links), how results are sorted or limited, or whether there are any usage constraints. For a tool that fetches dynamic data like news, more context is needed to use it effectively.

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 has 100% description coverage, with the single parameter 'lr' documented as 'language region, ex: en-US'. The description adds no additional meaning about parameters beyond what the schema provides, such as explaining why this parameter is required or how it affects the news results. With high schema coverage, the baseline score of 3 is appropriate.

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 states the tool's purpose as 'get sport news from Google News' with a specific verb ('get') and resource ('sport news'), making it immediately understandable. However, it doesn't explicitly differentiate itself from sibling tools like 'business', 'entertainment', or 'world' which likely serve similar news-fetching functions for different categories.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'search', 'latest', and category-specific tools (e.g., 'business', 'health'), there's no indication whether this tool is for general sports news, breaking sports news, or how it differs from a broader search function. No exclusions or prerequisites are mentioned.

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