Get forward estimates

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

Annotations declare readOnlyHint: true, and the description reinforces 'Read-only.' It adds behavioral context by detailing derived P/E and PEG calculations from the latest close, which goes beyond the annotation alone.

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, front-loaded with the primary action, and contains no unnecessary words. Every sentence adds value.

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 adequately explains the returned data: consensus estimates, management guidance, revision percentages, and derived P/E/PEG. It is comprehensive for a tool with 3 parameters and moderate complexity.

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%, so the schema already explains all parameters. The description reinforces the ticker requirement ('one exact Bullrun ticker') but adds no new parameter details beyond what the schema provides.

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 'Fetch forward consensus revenue/EPS/EBITDA estimates...' with a specific verb and resource (forward estimates for a Bullrun ticker). It distinguishes from siblings like get_financial_history or get_earnings_call_transcript by focusing on forward estimates and derived P/E/PEG context.

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 implies usage by stating 'for one exact Bullrun ticker' but does not explicitly state when not to use the tool or suggest alternatives. No guidance on when to prefer this over siblings like get_financial_history is provided.

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