explain_price_move

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description adds substantive context by listing the computed analytics (RSI-14, SMA-20/50/200, MACD, ATR-14, 30-day vol, gap/range vs ATR, earnings surprises) and the "today" freshness scope. It does not mention data sources, latency, or result shape, but with annotations present that is a minor gap.

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?

Two sentences, front-loaded with the purpose before the indicator inventory and the exclusion clause. The indicator enumeration is long but each item earns its place by telling the agent what the output will contain in the absence of an output schema.

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 carries the burden of describing returned content, and it does so by enumerating the technical and catalyst signals. Gaps remain around the historical lookback window and the response structure, but nothing needed to invoke the tool correctly 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?

Schema description coverage is 100% and the sole parameter's schema already gives accepted ticker formats (AAPL, BRK-B, BTC-USD, EURUSD=X). The description only reinforces the single-ticker scope ("a single ticker") without adding format or validation detail, so the baseline 3 applies.

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 a specific verb+resource ("Technical and catalyst attribution for why a single ticker moved today") and enumerates the exact indicators and signals produced. It also names what it does not cover (fundamental multiples, option chains), which routes the agent away from get_options_chain and analyze_ticker.

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?

"Use for technical and catalyst analysis" plus two explicit exclusions gives a clear selection rule. It stops short of naming sibling tools directly (e.g., "for option data use get_options_chain"), so the agent must infer the handoff from capability wording.

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