fetch_latest_news

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

No annotations exist, so description carries full burden. It discloses that sentiment is returned per item, which adds behavioral context. However, it does not mention side effects, rate limits, auth needs, or behavior on invalid symbol. Some transparency but limited.

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?

Extremely concise single sentence that front-loads the key information. No wasted 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?

With 1 parameter, no output schema, and no annotations, the description lacks details about return format (fields, structure, count), pagination, or error handling. Agent cannot fully infer what to expect from the response.

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 has 1 parameter 'symbol' with 0% description coverage. The description does not add any meaning beyond the parameter name. For a single parameter with no schema description, the tool description should compensate but fails to do so.

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 'Latest news items for one symbol with per-item sentiment' clearly states the verb (fetch), resource (latest news), scope (for one symbol), and a key feature (per-item sentiment). It distinguishes from sibling tools like fetch_market_news (broader scope) and analyze_news_sentiment (analysis on existing news).

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?

No guidance on when to use this tool vs alternatives. No prerequisites, exclusions, or context provided. The description only states what it does, not when it's appropriate to call it.

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