search_news

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does not mention whether the tool is read-only, any rate limits, pagination behavior (beyond per_page max of 25), or effects on data. The description only hints at the return value (news_search_id) but lacks deeper behavioral context.

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 extremely concise: one sentence stating the purpose, a tip, and a note about the return value. It is front-loaded with essential information and contains no unnecessary words.

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 has 14 optional parameters and no output schema, the description covers the main purpose, usage tips, and integration with sibling tools. It does not explain parameter interactions or result structure, but the rich schema descriptions partially compensate. The description is reasonably complete for guiding initial use.

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%, with each parameter having a description. The tool description adds marginal value beyond the schema by explaining the purpose and linking to other tools, but does not elaborate on parameter semantics or constraints. Baseline 3 is appropriate.

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 searches company news and press releases, and mentions related tools for filter values and a follow-up lookup, distinguishing it from siblings like lookup_news, get_news_categories, and get_news_galleries.

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?

Provides a tip to use get_news_categories and get_news_galleries for valid filter values, and mentions the returned news_search_id for use with lookup_news. This gives clear guidance on how to use the tool effectively, though it does not explicitly state when not to use it.

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