create_scatter_plot

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

With no annotations, the description should disclose behavioral traits. It mentions output options (svg/png) but fails to address side effects, permissions, data validation, or processing behavior. The core creation action is stated, but additional important behavioral details are missing.

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 structured as a clean parameter list with concise explanations. While slightly lengthy due to nine parameters, it is front-loaded with the purpose and efficiently uses bullet-like syntax. No unnecessary words.

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 (not shown), the description need not detail return values. However, it lacks information on requirements, error conditions, or data constraints. For a complex tool with many options, it feels slightly incomplete, but covers the basics adequately.

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?

The schema has 0% description coverage, so the description provides critical meaning for each parameter (e.g., 'X data points', 'Optional point labels (for hover)'). It also documents allowed values for 'palette' and 'output', which are absent from the schema. This fully compensates for the schema gap.

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 'Create a scatter plot,' which is a specific verb and resource. The tool name and description immediately distinguish it from sibling tools like create_bar_chart, create_histogram, etc., making the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives such as create_line_chart or create_histogram. There is no mention of prerequisites, context, or exclusions, leaving the agent to infer usage without support.

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