get_market_news

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

No annotations are provided, so the description bears full responsibility for disclosure. It only states the data source (Google News) but does not mention any behavioral traits like rate limits, caching, update frequency, or the format of returned data.

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, consisting of two sentences including an example. It is front-loaded with purpose. Slightly more structure (e.g., breaking out parameter explanation) could improve it, but it is efficient.

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 is simple with one parameter and has an output schema (not shown). The description lacks details about return structure or any caveats. Given low complexity, it is minimally adequate but could be more complete with output format hints.

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 only parameter is 'limit', which lacks a description in the input schema (0% coverage). However, the description's example 'get_market_news(15)' clearly indicates that the parameter controls the number of news items returned, adding meaning beyond the schema.

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 retrieves the latest Indian stock market news from Google News. It includes an example usage. This distinguishes it from sibling tools like get_stock_news and get_sector_news by specifying the source and scope.

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 an example but does not offer guidance on when to use this tool over alternatives such as get_stock_news or get_sector_news. No explicit when-to-use or when-not-to-use instructions are given.

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