search_news

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Perform a search,' which implies a read-only operation, but it fails to describe return format, pagination, permissions, or any other consequences. This leaves the agent with insufficient information about what the tool actually does beyond the action.

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 sentence with a Korean translation, which is concise but overly terse. It lacks meaningful detail needed for correct tool usage, making it under-specified rather than efficiently informative. It has no unnecessary words, but it also fails to communicate anything beyond the bare minimum.

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 no output schema, no annotations, and a description that lacks details about results, pagination, or alternatives, the tool is not adequately contextualized. The many sibling tools create ambiguity that is not resolved, making the description incomplete for reliable selection and invocation.

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 covers all four parameters (query, sort, start, display) with descriptions, achieving 100% schema description coverage. The tool description adds no parameter-specific information, so the baseline of 3 applies.

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 action ('Perform a search') and the resource ('Naver News'), which is more specific than a tautology. However, the verb is generic and the description does not explicitly differentiate from sibling tools like search_blog or search_shop, aside from the resource name itself.

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?

There is no guidance on when to use this tool versus the many sibling search tools. No alternatives are mentioned, no exclusions or prerequisites are stated, and the description merely restates the function without providing any decision-making context.

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