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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true and destructiveHint=false, and the description usefully reinforces this by promising no market-data fetching. It says nothing about the rights_confirmed gate, what "private analysis" means operationally, or limits on supplied data size/format, so genuine behavior beyond annotations is thin.

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 short sentences with the key constraint front-loaded after the action; there is little waste. "For private analysis" is the only phrase that does not clearly earn its place, since it does not tell the agent anything actionable.

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?

An output schema exists, so return values need not be described, but a 9-parameter tool with zero schema coverage needs the description to carry the parameter and prerequisite burden and it does not. An agent cannot tell from this text how to populate the two data-supply paths or what rights_confirmed governs.

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?

There are 9 parameters with 0% schema description coverage, and the description never explains rate, expiry, dividend_yield, rights_confirmed, source_format, or how source_data/source_text/data_source relate. Only a loose mapping is inferable (SYNTH to symbol, user-supplied chain to the source_* fields), which does not compensate for the coverage gap.

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?

It gives a specific verb pair ("Summarize" / "analyze") and the resource (an option chain), and clarifies that SYNTH is the default subject versus a user-supplied chain. However, "analyze" and "private analysis" are vague, and nothing distinguishes this snapshot-creation/summarization step from siblings like option_validate_snapshot or option_strategy_from_snapshot.

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?

"This service never fetches market data" implicitly tells the agent to supply source_data/source_text or rely on SYNTH, which is useful routing context. There is no explicit when-to-use/when-not-to-use guidance and no named alternative for validation, import, or strategy derivation.

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