get_earnings_results_this_week

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds valuable behavioral details: results are from the past, grouped by day, include headline P&L, dividend, and progress vs forecast. It also discloses cache-only behavior and Free plan delay, providing complete transparency.

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 well-structured: a concise purpose statement, followed by usage guidance, supported plans, and parameter documentation. It is front-loaded and contains no redundant information, effectively using space.

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?

Given the presence of an output schema, the description sufficiently covers returns by mentioning included financial items. With only two optional parameters and comprehensive annotation coverage, the description leaves no ambiguity about the tool's functionality.

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 0%, so the description compensates by explaining the two parameters date_from and date_to with format and default behavior. This adds sufficient meaning beyond the input schema, though it could include more examples or boundary details.

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 retrieves earnings results disclosed in a date window, grouped by day. It specifies the verb 'get' and the resource 'earnings results this week', and explicitly distinguishes from sibling tools like get_earnings_this_week and get_fins_summary.

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 provides explicit when-to-use guidance, including alternatives: 'For the upcoming SCHEDULE use get_earnings_this_week; for one stock's full financials use get_fins_summary.' It also mentions supported plans and Free plan limitations.

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