search_news_advanced

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

With no annotations provided, the description carries the full behavioral burden, but it mostly re-describes parameter formats rather than behavior. The only behavioral disclosures are has_coin's filtering semantics and the limit cap of 100; return shape, ordering, pagination, and error behavior are not mentioned.

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 front-loaded with a one-line summary and followed by a compact, readable Args list. Each line documents one parameter without fluff or repetition, making it appropriately sized for a five-parameter tool.

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?

Although all parameters are well documented, the tool has no output schema and no annotations, so the description should also clarify what the tool returns and when to prefer it over sibling search tools. Those elements are missing, leaving the overall context incomplete for an agent deciding whether and how to invoke it.

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 0%, but the description compensates thoroughly: every one of the five parameters is explained with formats or examples, including 'BTC,ETH' for coins and 'news:Bloomberg,Reuters;listing:' for engine_types, plus the max-results cap. This meaningfully exceeds what the bare schema provides.

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 opens with 'Advanced news search with multiple filters' and lists the filtering parameters, making the verb and resource clear: search news with coin, keyword, engine, and coin-presence filters. It does not explicitly contrast itself with sibling tools like search_news or search_news_by_coin, so sibling differentiation is absent.

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 word 'Advanced' and the enumeration of 'multiple filters' imply this tool is for filtered or complex news queries. However, there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as search_news or get_latest_news, leaving selection between siblings to inference.

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