market_news

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

Describes return value: up to 10 recent articles with title, publisher, link. No annotations, but description adequately conveys read-only behavior and output format.

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?

Two-sentence purpose, followed by clear args documentation and examples. No redundant information, front-loaded with key action and scope.

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?

For a simple one-param tool with an output schema, the description covers purpose, parameter semantics, usage examples, and return format. Complete and self-contained.

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?

With 0% schema coverage, the description explains the symbol parameter's purpose, optionality, and default behavior (empty for general news). Adds meaning beyond the schema's basic type/default.

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 it gets the latest market news for a stock or general market, with specific verb and resource. It distinguishes from sibling tools focused on quotes, fundamentals, etc.

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?

Provides clear usage context: optional symbol for company news, empty for general. Examples illustrate usage. No explicit alternatives, but context is sufficient given the tool's unique role among siblings.

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