origin_plot_scatter

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

Without annotations, the description carries full burden but only says it imports and plots. It does not disclose whether it modifies existing graphs, side effects (e.g., overwriting), or what the tool returns. The output schema exists but the description adds no behavioral context.

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 very concise with a single sentence, but it lacks structure for a complex tool. It front-loads the purpose, but does not convey essential parameter info or usage steps.

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 tool has 22 parameters and many sibling plotting tools, the description is severely incomplete. It fails to mention that it can import from various file types, customize axes, or control errors, making it hard for an agent to invoke correctly.

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 0% schema description coverage, the description must explain parameters but provides none. The one sentence gives no hint about path, columns, or any of the 22 parameters, leaving the agent completely uninformed.

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 imports table data and creates a scatter graph, which is a specific verb-resource pair. It distinguishes from sibling plotting tools by specifying 'scatter', but could be more explicit about being the dedicated scatter plot tool.

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?

No guidance is provided on when to use this tool versus alternatives like origin_plot or origin_plot_auto. The description does not mention exclusions or preferences.

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