render_chart_svg

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

No annotations are provided, so the description bears full responsibility. It discloses that the tool performs server-side rendering and can accept overlays from 'detect_patterns', but does not describe output details, side effects, prerequisites, or potential errors. The behavioral profile is adequate but not thorough.

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 concise and front-loaded with the core purpose. It conveys essential usage rules without unnecessary repetition, though it could benefit from clearer structuring.

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?

Given the tool's 22 parameters and no output schema, the description lacks details on return type (SVG vs. PNG), parameter interactions, and examples. It sufficiently links to sibling tools 'prepare_chart_data' and 'detect_patterns' but leaves many usage scenarios uncovered.

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?

The description mentions overlays and optional indicators as groups but adds little individual parameter meaning. With 22 parameters and only 41% schema description coverage, the description should compensate but does not, leaving many parameters under-explained.

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 the tool generates candlestick/line charts as SVG/PNG on the server side, distinguishing it from the client-side alternative 'prepare_chart_data'. The purpose is specific and actionable, though the output format (SVG string vs. PNG file) is not explicitly clarified.

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 explicitly advises to prioritize 'prepare_chart_data' for client-side rendering, restricts usage to explicit user requests for SVG/PNG save, and prohibits spontaneous calls. It also instructs to include indicators only when the user explicitly requests them, providing clear when-to-use and when-not-to-use guidance.

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