get_news

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

No annotations are provided, so the description carries full burden. It fails to disclose behavioral traits like read-only nature, rate limits, data freshness, or authentication requirements. For a news tool, such information is important for proper agent behavior.

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 concise and well-structured: a one-sentence purpose, a usage note, then clearly separated Args and Returns sections. Every sentence serves a purpose with no superfluous text.

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's simplicity (2 optional parameters) and the existence of an output schema, the description provides adequate context. However, the lack of behavioral transparency (rate limits, updates) leaves a gap. The Returns description is vague, but since an output schema exists, it's partially excused.

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 has 0% description coverage, but the description adds meaningful information: it lists values for 'category' (general, forex, crypto, merger) and explains 'limit' as number of items with default 10. This adds value beyond the schema, though it doesn't enumerate all possible categories.

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 'Get latest market news' with a specific verb and resource. It distinguishes itself from sibling tools which are mostly technical indicators (e.g., get_rsi, get_macd), making its purpose unique.

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 advises to use it 'to understand what's happening in the markets right now' and explains that news can explain price movements and predict trends. While it doesn't explicitly state when not to use, the context of sibling tools implicitly suggests using this for news vs. technical analysis.

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