export_to_datawrapper

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

Since no annotations are provided, the description carries the full burden. It discloses that the tool creates and publishes a chart, and lists supported chart types. However, it does not mention potential side effects (e.g., overwriting existing charts), rate limits, or failure behavior. The information is adequate but not exhaustive.

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 concise and well-structured: it opens with the core purpose, then provides necessary details (API token requirement and supported chart types). Every sentence adds value with no redundancy.

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 presence of an output schema (so return values need not be described), and 100% schema coverage, the description covers essential context (environment variable, chart type options). It is mostly complete for an external export tool, though missing error handling details.

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?

With 100% schema description coverage, the parameters are already documented. The description adds value by explaining that 'data' should come from get_resource_data() and by listing all supported chart types for the chart_type parameter, enhancing clarity beyond the 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 description clearly states the tool's purpose: exporting data to Datawrapper to create charts, publish them, and return embed URLs. It distinguishes from sibling tools like create_chart and export_data by specifying the external platform and embed output.

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 mentions the required environment variable but does not provide guidance on when to use this tool versus alternatives (e.g., create_chart for internal charts or export_data for raw data). No explicit usage scenarios or exclusions are given.

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