get_chart_reference

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

No annotations are provided, so the description carries the full burden. It implies a read-only documentation lookup, which is inherently low-risk, but discloses nothing about volume, pagination, or output size for what is billed as 'full reference documentation.'

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 sentences, zero filler, with the core action front-loaded and the prerequisite sequencing placed second. 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?

For a single-parameter, read-only documentation fetch with no output schema, the definition covers what an agent needs to invoke it correctly. It could go slightly further by noting that the response is a large reference document rather than a short answer, which would help an agent decide between this and a search tool.

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 100%, so the chartType keyword and its example values are already documented in the schema. The description adds only the routing hint to list_chart_types, which is a usage rather than a semantic contribution. Baseline 3 applies.

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?

States a specific verb (Get) and resource (full reference documentation for a specific amCharts 5 chart type). The scope 'chart type' distinguishes it from general-purpose siblings like get_doc, get_api_reference, and get_section without needing to open a schema.

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?

Explicitly prescribes the workflow: 'Use list_chart_types first to see available types,' naming the sibling that supplies valid values. It does not, however, say when to prefer this over get_api_reference or get_core_reference for overlapping reference needs.

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