render_candle_pattern_diagram

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

No annotations provided, so description carries full burden. It discloses key constraints: no automatic calls, output is widget code, educational purpose. Does not mention side effects or authorization, but for a rendering tool this is sufficient.

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 fairly concise, front-loaded with purpose and usage rules. Some redundancy with brackets and Japanese/English duplication, but overall efficient.

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?

For a visualization tool with nested schema and no output schema, the description covers when to use, what it does, and how to handle output. Missing return value details but adequately complete for correct invocation.

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 75%, so baseline is 3. The description does not add significant parameter info beyond schema; it gives usage context but no new semantics for individual parameters.

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 clearly states it renders an educational candle pattern diagram, visualizing results from analyze_candle_patterns for beginners. It distinguishes from siblings like render_chart_svg by specifying it's for pattern education and only when user explicitly requests.

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?

Explicitly says use only when user says 'show me a diagram' etc., and prohibits spontaneous invocation. Also provides precise instructions for output handling: pass data.svg to Visualizer widget, no direct SVG output.

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