render_plotly

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

With no annotations beyond title, the description effectively discloses key behaviors: output types (link returns localhost URL, filepath saves to disk, raw returns base64), custom styling options, and examples. It does not mention error cases or side effects, but the rendering behavior is well explained.

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 well-structured with bullet points and examples. It is relatively long but each section adds value: purpose, output options, multiple examples. Front-loaded with the main purpose.

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 has 12 parameters and no output schema, the description covers the required plotlyCode, output formats, styling, and return behavior for each output type. It could mention that the localhost URL is temporary or that file path requires write permissions, but overall is complete enough.

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?

Despite 0% schema description coverage, the description adds significant meaning by explaining output options, format, and styling parameters (backgroundColor, width, height). The example code illustrates the required plotlyCode structure, compensating for the lack of per-parameter descriptions.

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 Plotly charts to multiple formats (SVG, PNG, JPG, PDF). It distinguishes from sibling tool render_mermaid by focusing on Plotly, a different charting library.

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 provides explicit usage guidance through examples for different output options (link, filepath, raw) and mentions the required plotlyCode. It implicitly differentiates from render_mermaid but does not explicitly state when not to use this tool.

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