publish_chart

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

Annotations indicate modification (readOnlyHint=false) and idempotency (idempotentHint=true). The description adds context about the effect: making the chart publicly accessible and rendering a preview in chat, which is beyond what annotations provide. No contradictions.

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 short and front-loaded with the purpose. The initial '⚠️ DATAWRAPPER MCP TOOL ⚠️' line is slightly redundant but not harmful. Overall concise and to the point.

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 simple publish action with 2 parameters and no output schema, the description covers the main effect and usage guidelines. It lacks details on edge cases (e.g., already published) but is generally complete for typical use.

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?

Input schema coverage is 100%, and schema descriptions are adequate for both parameters. The description does not add extra parameter details beyond the schema, so 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?

The description clearly states 'Publish a Datawrapper chart to make it publicly accessible and render a preview in chat,' using a specific verb and resource. It distinguishes itself from sibling tools like create_chart, delete_chart, etc., by being the only tool that publishes.

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 explicitly provides usage guidelines: 'Only use this tool when the user explicitly requests to publish the chart. Do not automatically publish charts after creation unless specifically asked.' This clearly tells when and when not to use the tool.

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