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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety is covered. The description adds meaningful behavioral context: estimates shift as dates near and the data mirrors the Market Hub display. No contradiction with annotations.

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 concise, front-loaded sentences. The first sentence delivers the core definition, the second contextualizes the data source, and the third clarifies the dynamic nature. Every word earns its place.

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?

Covers what data is returned (EPS, revenue, analyst counts), horizon types (quarterly/annual), and the caveat about estimates shifting. No output schema exists, but the description gives sufficient understanding for an agent. Exact return format is not specified, but that's acceptable given the concise scope.

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 descriptions cover 100% of parameters, setting a baseline of 3. The description reinforces 'per horizon' and overviews data fields, but it doesn't add syntax or parameter-specific meaning beyond what the schema already 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?

States clearly it provides analyst earnings estimates for upcoming quarters and fiscal years, listing specific data components (EPS consensus, revenue, analyst counts). 'Estimates, not forecasts' distinguishes it from prediction tools. While it doesn't explicitly differentiate from siblings like get_earnings_transcript, the resource type is unambiguous.

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?

Provides usage context such as covering both quarters and fiscal years, and a caution that estimates are not forecasts. However, it lacks explicit when-to-use guidance or mention of alternative tools. The intended use is implied but not stated as a rule.

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