Earnings Move Analysis

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

Annotations already indicate readOnlyHint=true, and the description aligns with that by using non-mutating language like 'analyze' and 'returns'. It adds useful behavioral context about the kinds of outputs each analysis mode produces, without contradicting the annotation.

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?

Description is well organized with a short purpose statement, an explicit use-case sentence, and a compact Args section. The seven bullet points are slightly long but necessary to disambiguate the analysis argument.

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?

There is no output schema, so the description's note about returning 'the selected earnings analysis payload with a compact summary' is helpful but abstract. For the selection task, the mode-specific descriptions and parameter guidance give the agent enough context to invoke the tool 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 description coverage is 0%, so the description carries full responsibility for explaining parameters. It clearly explains ticker, the seven analysis options, and the comma-separated day horizons for periods, including defaults and scope.

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 states exactly what the tool does: analyze stock moves around earnings and whether options misprice them. It further distinguishes itself from broad earning-domain siblings by listing seven specific analysis modes tied to this tool.

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 explicitly says when to use this tool: when users ask whether earnings options are over/underpriced, how a stock usually moves on earnings, or if a straddle is worth buying. It does not mention alternatives or when not to use it, but the use-case guidance is clear enough.

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