get_company_news

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

The description indicates a read operation (get news) with no destructive hints. However, without annotations, it does not disclose details like rate limits, pagination, or source of news, leaving some behavioral ambiguity.

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 short and mostly clear, though the Args block duplicates schema information. The core purpose sentence is well-placed. Minor redundancy but no unnecessary verbosity.

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?

For a simple tool with 2 parameters and no output schema, the description covers the basic function. It is missing output format details (e.g., headlines vs. full articles) and potential constraints, but is minimally adequate.

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?

With 0% schema coverage, the description adds semantic value by explaining each parameter: 'Company name to search for' and 'Number of articles to return (default: 3)'. This compensates for the bare schema (which only has titles).

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 gets company-specific news, with examples (e.g., ZoomInfo, 6sense). It distinguishes from siblings like 'get_marketing_news' (broader marketing news) and 'web_search' (general web results).

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?

No explicit guidance on when to use this tool versus alternatives. The description implies it is for company-specific news, but lacks when-not-to-use criteria or references to sibling tools.

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