Get market news

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It goes beyond a simple verb+object by revealing two useful behaviors: results are de-duplicated and sorted newest-first, and the source is Google News. It does not mention pagination, rate limits, or output format, but for a simple read-only news tool this is reasonably transparent.

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, compact sentence that immediately communicates the source, scope, and ordering behavior. Every phrase carries meaning and there is no redundant or filler content.

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 tool's simplicity—one optional parameter, no nested objects, no output schema—the description gives an agent enough context to call it correctly. It names the resource, the source, and the processing guarantees, which is complete for this use case.

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 for the only parameter, 'limit', including its default and maximum. The description adds no parameter-specific details, but none are needed because the schema already fully explains the parameter.

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 names a specific resource ('Uruguayan dollar/economy headlines'), a clear source ('Google News'), and key processing behavior ('de-duplicated and newest first'). This clearly distinguishes it from the sibling tools like get_rates or list_houses, which address different domains.

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 phrase 'Latest ... headlines' implies the tool should be used when current market news is needed, and the scope is clearly Uruguayan. However, there is no explicit guidance about when not to use it or which sibling tool to choose instead, leaving the agent to infer selection from context.

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