news

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

No annotations provided, and the description contains no information about behavioral traits such as what the tool returns, whether it mutates data, or any side effects. The description adds no value beyond the already sparse name.

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 overly brief (3 words) and lacks a front-loaded, informative summary. While concise, it sacrifices essential detail, making it inadequately sized for proper tool comprehension.

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?

Despite 7 parameters and no output schema or annotations, the description offers no context about return values, pagination, or intended use. It leaves significant gaps in understanding the tool's purpose and behavior.

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 input schema adequately documents all parameters. The description adds no additional meaning, but the baseline score of 3 is appropriate given the schema richness.

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 'News search tool' is a tautology that merely restates the tool's name. It does not specify a verb, resource, or scope, nor does it differentiate the tool from sibling tools like 'search' or 'trending'.

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. It does not mention any prerequisites, exclusions, or contexts where this tool is preferred over siblings.

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