render_chart

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

With no annotations provided, the description carries the disclosure burden and does substantial work: it states the return shape (metadata plus inline image), default output and data-root paths, and side effects like force-overwriting existing files and keeping generated HTML in tmp/. Minor gaps remain around failure behavior and exact metadata fields, but the main behavioral profile is disclosed.

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?

One purpose sentence is followed by a compact Args list with no filler. Every bullet adds a default, constraint, or side-effect detail, and the main deliverable is front-loaded before parameter details.

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?

There is no output schema or annotations, so the description must stand alone. It covers every parameter, default, constraint, and side effect, and references charting://schema for the nested spec object. The lack of detailed return-metadata fields is a minor gap compared to the breadth of information supplied.

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 input schema has 0% description coverage, but the Args block fully compensates: it documents all eight parameters, explains defaults for out and home, constrains theme to light/dark and scale to 1-4, clarifies force as overwrite behavior, and points spec to the charting://schema resource. This adds meaning far beyond the bare schema.

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 opening sentence names a concrete action and artifact: 'Render a chart spec to a PNG and return metadata plus the inline image.' This clearly distinguishes render_chart from validate_spec and chart_component, which are not about producing a PNG from a spec.

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 gives no when-to-use guidance, exclusions, or alternatives. An agent must infer usage solely from the purpose statement; there is no hint such as 'use validate_spec to check the spec first' or when chart_component would be more appropriate.

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