Get news, filings & earnings

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

Annotations already declare readOnlyHint and openWorldHint, so the description does not need to repeat those. It adds a useful structural detail about the 'data' field containing news, filings, and earnings, which gives a hint about the response layout. No contradictory behavior is disclosed, but other behaviors like rate limits or error handling are not mentioned.

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 two sentences, starts with the core action ('Combined event view'), and every phrase adds meaning. It avoids redundant wording and is appropriately sized for a simple tool.

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 description adequately explains the tool's purpose and what it returns (news, filings, earnings) without an output schema. It lacks details like time ranges or pagination, but for a read-only aggregate with a single parameter, it is sufficiently complete for an agent deciding when to use it.

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 input schema has only one parameter (ticker) and no description in the schema. The description mentions 'for a ticker' but does not provide any additional context about the format, examples, or constraints. With 0% schema coverage, the description should compensate more, but it barely does.

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 it is a combined event view for a ticker containing news, filings, and earnings. It explicitly differentiates from sibling tools like stoquant_get_news and stoquant_get_sec_filings by emphasizing the combined nature and positioning itself as 'the single best call' for a holistic view.

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 a clear usage context—'what is happening with this stock'—and implies this is the go-to tool for a combined snapshot. However, it does not explicitly name alternatives or state when to avoid using this tool, only implicitly distinguishing from single-data-type tools.

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