chartimg_v1_advanced_chart_storage

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

With zero annotations, the description carries the full disclosure burden. It does reveal meaningful behavior: the operation mutates state ('save'), the data lands in 'public storage' (a visibility/exposure fact), and it returns JSON with a `url` plus a retrieval endpoint. However, it omits idempotency/overwrite semantics, any auth or rate-limit caveats, and retention or exposure implications — material gaps for a storage-mutation tool.

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?

A single front-loaded sentence: the verb 'save' and the resource appear immediately, followed by the output contract and endpoint. There is no filler, no repetition of schema content, and every clause 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?

This is a 14-parameter mutation tool with no annotations, no output schema, and almost no schema-level parameter descriptions. The description covers the purpose and the return shape but says nothing about how to select or format the numerous inputs. For an agent to invoke it correctly on a realistic call, the parameter semantics gap is critical and unaddressed.

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 only 21%, so 11 of 14 parameters (logo, style, theme, width, format, height, symbol, timezone, watermark, watermarkSize, watermarkOpacity) have no semantics anywhere. The description adds zero parameter guidance and thus fails to compensate for the low coverage, leaving an agent to guess at the meaning and format of most inputs.

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 and resource ('save an **advanced** chart to public storage') and discloses the output contract (JSON with `url`). The qualifier 'advanced' and the version marker 'v1' implicitly separate it from siblings like chartimg_v1_mini_chart_storage and chartimg_v2_advanced_chart_storage, but no sibling is named explicitly and the boundary against v2/layout variants is left to inference.

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?

There is no when-to-use guidance, no named alternatives, and no conditions for choosing this over chartimg_v1_mini_chart_storage, chartimg_v2_advanced_chart_storage, or the _image variants. The word 'advanced' provides only an implied scoping signal; an agent must infer the choice from the tool name rather than from the description.

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