get_analyst_estimates

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real behavioral context the annotations cannot: dual output formats and, importantly, what happens for a stock with no analyst coverage (N/A fields or a short message) rather than an error.

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?

Three short paragraphs, front-loaded with what the tool returns, then usage and sibling disambiguation, then output/edge-case behavior. Every sentence carries information an agent would otherwise have to guess.

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 tool is simple (2 params, no nesting), an output schema exists, and annotations cover the safety profile, so the description need not describe return structures. Combined with the no-coverage fallback note and format options, nothing material is missing.

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 already carries 100% description coverage for both parameters, including ticker examples and the response_format enum, so the baseline is 3. The description only adds the concrete effect of response_format='json' plus the default Markdown behavior, which is mild reinforcement rather than new meaning.

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 names a specific verb and resource ('Forward-looking analyst estimates for one stock') and enumerates the concrete contents: price targets, EPS and revenue estimates by period, and growth estimates. It is immediately distinguishable from the sibling get_analyst_recommendations, which is named explicitly.

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?

It gives an explicit selection rule ('Use for projected/expected numbers and forecasts') and then routes the agent between two siblings: recommendations/rating trend goes to get_analyst_recommendations, numeric forward estimates go here. That is exactly the when-to-use / use-instead-of guidance an agent needs.

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