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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered; the description adds real behavioral detail on top: the composite contents and the quiet-window fallback ('says when the stock last had news' rather than returning empty). It does not mention latency, cost, or rate limits for this multi-source aggregation, which matters for a composite call.

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?

Front-loads the payoff ('Everything MoveSurge has on one stock in one call'), then enumerates contents in a single dense list, then closes with the trigger phrase. No filler sentences and nothing repeated from the schema or annotations.

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 an output schema present, the description needn't explain return structure, and annotations cover safety, so remaining gaps are small. It is complete enough to decide when to call, though it doesn't clarify how this differs from overlapping siblings such as explained_moves or event_screen for the same ticker.

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 coverage is 100% — ticker, days (1-30, default 7), and limit (1-25, default 10) are all documented with ranges and defaults. The description's 'recent headlines' and 'if the window is quiet' loosely tie to days/limit but add no syntax or format detail beyond the schema, so 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 concrete resource (one stock) and enumerates exactly what the single call returns: headlines with before/after price, largest own move, earnings vs estimates, next report date, and any investigation. This clearly separates it from market-wide siblings like market_brief and from narrower ones like search_headlines or earnings.

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?

Gives an explicit trigger phrase ('what's going on with NVDA'), which tells the agent the intended intent class. It stops short of naming alternatives or exclusions (e.g. use search_headlines for multi-ticker, market_brief for the whole market), so routing must be inferred.

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