get_earnings_news

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

The description discloses the filtering behavior (applies keyword filter to the full news feed) and the source (Finviz), which is vital since no annotations are provided. However, it does not explicitly state that this is a read-only operation or mention any potential rate limits or data freshness caveats, but the 'get' verb implies read-only and the filtering detail is sufficient for basic understanding.

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 compact, front-loaded with the core purpose, then usage guidance, then parameter details. Every sentence adds value—no filler or redundancy, making it efficient for an agent to parse.

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 tool with only two parameters and a straightforward filtering operation, the description covers purpose, usage, filtering logic, and parameter semantics fully. The presence of an output schema means the description doesn't need to detail return format, and no critical gaps remain for correct invocation.

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 has no descriptions for ticker or count, so the description's 'Args' section fully explains both: ticker as a symbol and count as the number of headlines with a default of 10. This compensates completely for the 0% schema coverage and adds meaning beyond the raw 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 fetches earnings-related headlines for a stock from Finviz, and lists the specific filtering keywords. This distinguishes it from the sibling get_stock_news, which returns all news. The verb 'get' and resource 'earnings-related headlines' are precise and unambiguous.

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?

Explicitly states when to use this tool ('post-earnings analysis' or 'building an earnings update') and when not to, directing users to get_stock_news for general news. This gives an agent clear routing logic without needing to infer from context.

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