Get forward estimates

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

Despite annotations being present, the description adds substantial behavior context: a free on-demand background refresh stores at most one snapshot per day, the first read may be empty, fiscal periods and source currency are preserved, forward P/E/PEG only applies when quote and EPS currency units match, and the tool does not modify portfolios or user data. This also explains the readOnlyHint=false annotation via the snapshot-writing refresh.

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?

Front-loaded with the core read operation and kept to four dense sentences, each carrying distinct information (data scope, refresh/staleness, gaps, currency caveat). Slightly over-packed with niche P/E/PEG currency detail, but no sentence is pure filler.

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?

With no output schema, the description does outline the returned content (revenue/EPS estimates, EPS revision percentages, preserved fiscal periods and currency) and warns of empty first reads. It stops short of describing row structure or how annual vs quarterly rows are shaped, but is sufficient to call correctly.

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% and the ticker format caveats (suffixed vs bare codes, resolving ambiguous listings) live in the schema itself, so the schema already does the heavy lifting for all three parameters. The description reinforces the 'exact ticker' constraint and period/currency preservation but adds no syntax or constraint detail beyond the schema, matching the baseline for full coverage.

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?

States a specific verb and resource (read cached Yahoo analyst consensus revenue/EPS estimates plus EPS revision percentages) scoped to one exact Bullrun ticker, and explicitly bounds the coverage (no EBITDA, management guidance, or revenue revisions). This distinguishes it from generic fundamentals/valuation siblings without ambiguity.

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?

Usage is implied by the resource scope ('one exact Bullrun ticker') and the note that the first read may be empty, but the description never names alternatives such as get_financial_history or get_valuation_model, nor when to prefer this tool over them. The reader must infer routing from the sibling list.

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