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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful non-annotation context: paid chart types require a Code or Complete licence key passed as the Bearer token, which is auth information an agent cannot get from the schema. It stops short of saying what happens when the key is missing or insufficient.

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?

Two tight sentences with no filler, and the payload description is front-loaded ahead of the licensing caveat. The first sentence is a verbless fragment, which reads slightly like a caption rather than an instruction.

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?

With only two parameters and no output schema, the description usefully enumerates what comes back (install command, component file, example file) and covers the licence requirement. The main missing piece is how this differs from the sibling spec/token tools, which matters given the near-identical naming.

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 coverage is 100% and both parameters (slug and the chart/widget/interactive enum) are documented in the schema, so the schema does the heavy lifting. The description only implicitly references 'one chart type' and says nothing about the 'with' variants, so it adds no meaning beyond the structured fields.

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 names the concrete artifacts returned for a single chart type: the install command, the component file, and an example file with sample data. That is specific enough to know exactly what the tool yields, though it never states a verb and does not distinguish the resource from get_chart_spec or get_tokens.

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 statement of when to reach for this tool instead of get_chart_spec, get_tokens, or search_charts, and no exclusions or prerequisites beyond the licence note. Usage is only inferable from the noun phrase describing the payload.

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