financial_news

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

No annotations are provided, so the description carries the full burden. It mentions 'Real-time' and 'licensed' but does not disclose behavioral traits like read-only nature, rate limits, pagination, or data freshness. The description lacks detail on what happens if no news is found or if the source is unavailable.

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 front-loaded with the purpose. The Args section is clearly formatted inline. While concise, it could be slightly more structured (e.g., bullet points), but it serves its purpose without unnecessary 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?

With 3 parameters and no output schema, the description covers the parameters adequately but lacks details on return format (e.g., what fields each news item contains), pagination, or error handling. Given the tool's simplicity, it is minimally viable but has clear gaps.

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%, so the description must provide meaning. It explains each parameter: symbol ('Optional symbol filter... None = all news'), category ('News category...'), limit ('Max number of news items'). This adds significant context beyond the schema's type and default values.

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 provides 'Real-time financial news via Marketaux (licensed).' It specifies the resource (financial news), verb (implied get), and source. Among many sibling tools focused on technical analysis or market data, this is the only news tool, making its purpose distinct.

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 explains the parameters and their defaults, providing context for usage (e.g., filter by symbol, category, limit). However, it gives no explicit guidance on when to use this tool versus alternatives or when not to use it. The context of sibling tools being mainly technical analysis implies but does not specify exclusions.

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