Get News

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, covering the safety and side-effect profile. The description adds the Yahoo Finance source and recency ('most recent'), but does not disclose additional behavioral traits such as return format or pagination, which is acceptable given annotation coverage.

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—two sentences with no unnecessary words. The first sentence states the action and resource, and the second provides valuable usage context. Every sentence earns its place.

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 only two parameters, no output schema, and strong annotations. The description explains the purpose and use case adequately, and the absence of detailed return valua information is forgivable given the nature of the tool and that annotations cover safety.

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 description coverage is 100% for both parameters (symbol and count), so the baseline is 3. The description adds minimal parameter meaning beyond the schema, only referring to 'a given stock' which maps to symbol; it does not elaborate on count or formatting.

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 'Fetches the most recent news headlines for a given stock using Yahoo Finance,' which is a specific verb+resource combination. It is implicitly distinct from sibling tools since no other sibling tool covers news headlines.

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 clear usage context by stating it is 'Crucial for analyzing fundamental catalysts or identifying the source of technical momentum breakouts.' This tells the agent when to use the tool, though it does not explicitly mention alternatives or exclusions.

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