getStockNews

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's role in transparency is reduced. The description adds that it returns headlines, snippets, URLs, and tickers, but does not disclose pagination behavior, rate limits, or the fact that results are for all stock news without ticker filtering. No contradiction with annotations.

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 sentences, no redundant words. Front-loaded with the tool's purpose and what data is returned. Efficient and clear.

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?

No output schema exists, so the description should partially compensate. It lists return fields (headlines, snippets, URLs, tickers) but does not specify that the result is an array, nor does it mention that it returns news for all stocks (no ticker filter). Error handling or rate limits are not addressed. Adequate but not thorough.

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?

Input schema covers 100% of parameters with descriptions, so baseline is 3. The description adds no additional meaning beyond the schema; it mentions 'latest' but does not explain date parameter format or defaults. No extra semantic guidance.

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 the latest stock market news and lists the specific data returned (headlines, snippets, URLs, tickers). It uses a specific verb ('get') and resource ('stock market news'), and the name distinguishes it from sibling news tools for crypto, forex, or general 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?

The description implies use for stock news but does not explicitly state when to use this tool versus alternatives like getCryptoNews or getGeneralNews. No when-not-to-use or alternative recommendations are provided. Guidance on date range and pagination is implicit from the parameters but not articulated.

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