Earnings history

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description complements by detailing the data source (Item 2.02 filings) and pagination behavior. It adds context about auto-collection and ordering but does not describe return format, which is acceptable without an output schema.

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 cover purpose, source, pagination, and alternative. Every sentence adds information with no fluff. Front-loaded with primary purpose.

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 read-only list tool with 4 parameters and pagination, the description is sufficient. It explains what the tool does, how to use pagination, and how it compares to a sibling. No output schema, but the description doesn't need to detail return values as per guidelines.

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 coverage is 100% with descriptions for all parameters. The description adds value by explaining the interaction between cursor/limit and max_items, and that results are ordered most recent first, which is not in the schema's parameter descriptions.

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 lists earnings-release history sourced from 8-K filings, most recent first. It distinguishes from the sibling tool 'stocks_events' by specifying that this tool is for earnings only while 'stocks_events' covers all material events.

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 describes pagination methods (cursor/limit, auto-page with max_items) and provides a clear alternative: for all 8-K events, use stocks_events. This tells the agent when to use and when not to use this tool.

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