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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that plots are 'opaque PNG' and that SYNTH is computed from engine artifacts with no simulation/backtest. It does not disclose behavior like whether the tool requires rights_confirmed=true, how it handles invalid symbols, or what happens when rate/expiry are null. The added context is modest but not contradictory.

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 a single paragraph of three sentences, reasonably concise and front-loaded with the main action ('Render opaque PNG plots'). It includes useful context about SYNTH's limitations without excessive verbosity. It could be slightly more structured, but it earns its place.

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 10 parameters, 0% schema coverage, and an output schema present, the description is incomplete. It does not explain the role of most parameters, the meaning of the output schema, or how the tool handles the 'all' plot option. The SYNTH context is helpful but does not make the tool callable for non-SYNTH symbols or custom source data. The description leaves significant gaps for an agent 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 must compensate for 10 parameters, but it only mentions plot types and the SYNTH symbol. It does not explain the meaning of rate, expiry, data_source, source_data, source_text, source_format, dividend_yield, or rights_confirmed. The description adds no value for the vast majority of parameters, leaving the agent to guess their semantics.

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 a specific verb ('Render') and resource ('opaque PNG plots'), and enumerates the available plot types (market, Greek ladder, structure comparison). It does not explicitly distinguish itself from sibling tools like option_plots_from_snapshot or option_report_plots, but the mention of 'SYNTH sample' and 'engine artifacts' gives some context. It is clear enough to understand what the tool does, though sibling differentiation is weak.

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 implies usage by listing plot types and noting that SYNTH has no simulation/backtest because the hosted service has no price history. It does not explicitly state when to use this tool versus alternatives like option_plots_from_snapshot or option_report_plots. The context about SYNTH is useful but does not provide clear selection criteria among siblings.

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