plot_show_absolute_error

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

With no annotations, the description must disclose behavior itself. It only states that the tool shows the error on the Plot window and does not mention whether this modifies the plot state, requires an existing plot, toggles a display setting, or has 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.

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

The description is short and front-loaded: the first sentence states the operation and the second adds a helpful GUI equivalence. No filler is present, though it sacrifices behavioral detail for brevity.

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 display-mutating tool with no annotations and no output schema, the description leaves out prerequisites (e.g., plot must exist/window must be open) and any indication of return value or persistent effect. It is minimally usable but not complete.

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?

Schema description coverage is 100%, so plot_path and plot_number are already documented. The description adds the metric context (MAX/RMS) but does not elaborate on how plot_path or plot_number should be formatted, so it stays at the baseline.

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 names a specific verb ('Show') and object ('absolute error (MAX/RMS) on Plot window'), so an agent can understand the intended operation. It does not explicitly contrast with the sibling plot_show_relative_error, but the metric in the name and description makes the distinction reasonably clear.

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 given about when to use this tool instead of plot_show_relative_error, plot_setup, or plot_display. The phrase 'Equivalent to ShowAbsoluteError in IC-CAP GUI' gives a domain reference but no decision rule for selecting this tool.

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