fetch_market_news

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

With no annotations provided, the description bears full responsibility for disclosing behavioral traits. It does not mention whether the tool is read-only, rate limits, data freshness, pagination, or return format. It only lists parameter values without any 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 very brief, with two short phrases. It front-loads the primary purpose ('Broad market news') and then lists parameters. Every word earns its place, but it could be slightly more structured (e.g., sentence format).

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?

The tool has no output schema and only two parameters, but the description fails to describe what the tool returns (e.g., list of news articles, each with fields like title, source, etc.). Given the lack of output schema, the description should compensate by explaining the return structure, which it does not.

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 provides no enums, and schema_description_coverage is 0%. The description adds significant value by explicitly listing the allowed values for category (all, stock, sectoral, global) and sentiment (all, positive, negative, neutral). This compensates for the schema's lack of constraints, though it does not explain the meaning of each value.

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 fetches broad market news with parameters for category and sentiment, distinguishing it from sibling tools like fetch_latest_news (likely for symbol-specific news) and analyze_news_sentiment. However, it does not explicitly mention that it does not filter by specific symbols, leaving room for ambiguity.

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 provides no guidance on when to use this tool versus alternatives such as fetch_latest_news for symbol-specific news. It lacks any 'when-not-to-use' or context about prerequisites, making it difficult for an agent to decide without prior knowledge.

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