get_news_by_site

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 only states 'Find articles from a specific publisher site using Google News,' implying a read-only search but not mentioning side effects, external dependencies, rate limits, or how the result data is structured. The description does not contradict anything, but it is minimal.

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?

A single sentence that front-loads the verb and target resource with zero filler. The description is appropriately sized for its purpose and every word contributes to the meaning.

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?

The parameter schema and output schema cover the technical invocation and return structure, so the description need not repeat those. However, with no annotations and a large set of sibling tools, the description lacks explicit usage routing and deeper behavioral context. It is adequate but has clear gaps in 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?

The schema has 100% description coverage for its 5 parameters, so the baseline is 3. The description adds no additional parameter-level meaning beyond what the schema already provides. The parameter descriptions themselves handle site format, period, full_data, summarize, and max_results.

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 uses a specific verb ('Find') and resource ('articles from a specific publisher site'), making the tool's function immediately clear. The 'by site' scope distinguishes it from sibling tools like get_news_by_keyword and get_news_by_topic. No ambiguity or tautology.

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 implied usage is obvious from the description—use when you need articles from a particular publisher domain. However, it does not explicitly state when to choose this tool over the many sibling news tools, nor does it provide any exclusion criteria. The guidance is embedded in the wording but not directly addressed.

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