market_news

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

The description discloses the return format and the optional behavior when the symbol is left empty. It doesn't mention error handling or rate limits, but as a 'Get' tool, the read-only nature is implied.

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: purpose, return format, args, and examples. It is front-loaded and every sentence adds value.

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-parameter tool with an output schema present, the description covers purpose, parameter semantics, and examples sufficiently. No critical gaps remain.

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 schema only defines 'symbol' as a string with a default, but the description explains its meaning, optionality, and behavior when empty. Concrete examples with AAPL and RELIANCE.NS further clarify usage.

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 gets market news for a stock or the general market, with a specific return format (up to 10 articles with title, publisher, and link). This distinguishes it from sibling tools focused on quotes, historical data, or analysis.

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 optional symbol parameter and provides examples for both company-specific and general market news. It doesn't explicitly mention alternatives or when not to use it, but the usage context is clear.

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