Server Quality Checklist

Tool Scores

• generate_chartA
  3.5/5.0
  Behavior3/5

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

  The annotations already carry the mutation/open-world signals, and the description adds one extra behavioral fact: engine selection is decided automatically from chart type. However, it does not note side effects such as data being sent to an external engine or a share_link being publicly accessible, so disclosure is only partial.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  Two compact, front-loaded sentences contain the core action, the available output formats, and a useful implementation detail. There is no filler or repetition.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  The schema covers parameter semantics well, and the description states the main purpose and output modes. But given the missing output schema and the presence of a recommendation sibling, the description should also explain the expected workflow—e.g., when to call recommend_charts first and how the two dataset inputs relate—so the agent can plan correctly.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  All seven parameters have thorough descriptions in the schema, so the baseline is 3 and the description need not repeat them. The description does not add any parameter-specific semantics beyond what the schema already states.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description names a specific action ('Generates'), a concrete deliverable ('production-ready chart specification'), and the three possible return formats. This clearly differentiates it from the sibling tool recommend_charts, which would recommend chart types rather than produce the chart.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines2/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  No guidance is given on when to use generate_chart versus the sibling recommend_charts, or whether recommend_charts should be called first when preferred_chart_type is absent. The automatic-engine note is implementation detail, not usage direction.

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

• recommend_chartsA
  3.7/5.0
  Behavior3/5

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

  Annotations already cover read-only, idempotent, and non-destructive behavior, so the safety profile is clear. The description adds that the tool returns confidence scores and column classifications in addition to chart types, which goes beyond the annotations, but it does not disclose anything about output shape, limits, or side effects.

  Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

  Conciseness5/5

  Is the description appropriately sized, front-loaded, and free of redundancy?

  The entire description is a single, front-loaded sentence with no filler. It immediately states the action and then lists all relevant output categories in a compact, readable way, including the parenthesized column classification names.

  Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

  Completeness3/5

  Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

  The four parameters are all optional and there is no output schema, so an agent relies on the description to understand what will be returned. The description lists chart types, confidence scores, and column classifications, but it does not specify the return JSON structure, confidence scale, or how requiredColumns relates to optionalColumns. This leaves some ambiguity for programmatic use.

  Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

  Parameters3/5

  Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

  Schema description coverage is 100%, so each parameter is already documented. The description vaguely maps to user_intent and dataset_json/dataset_content with 'dataset structure or user prompt', but it adds no additional meaning about parameter formats, relationships, or precedence. Baseline 3 is appropriate.

  Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

  Purpose5/5

  Does the description clearly state what the tool does and how it differs from similar tools?

  The description uses a specific verb ('Analyzes') and clearly names the resource and outputs: dataset structure or user prompt, and the recommendations of chart types, confidence scores, and column classifications. This is distinct from the sibling generate_chart, which implies actually producing a chart rather than recommending one.

  Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

  Usage Guidelines3/5

  Does the description explain when to use this tool, when not to, or what alternatives exist?

  The description implies when to use the tool by saying it analyzes dataset structure or user prompt to make recommendations, but it never explicitly mentions the sibling generate_chart or says when not to use this tool. Context is present, but there is no direct guidance on alternatives.

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