overlay_plots

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

No annotations are provided, so the description carries the full burden. It describes that plots are composites onto a single set of axes, but does not disclose potential side effects (e.g., scaling behavior, how different plot types interact, or whether overlaid plots are modified).

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 two sentences, front-loaded with the core purpose, and includes a helpful analogy to dashboards. Every sentence adds value without redundancy.

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?

The tool has an output schema (not shown but indicated), so return values may be documented there. The description covers the main idea and distinguishes from siblings. However, it lacks details on prerequisites (e.g., plot IDs must exist) and edge cases.

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 coverage is 100%, so the schema already documents both parameters. The description adds no extra meaning beyond what the schema provides for 'plot_ids' (comma-separated) and 'title' (default 'Overlay'). Baseline 3 is appropriate.

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 overlays multiple plots on shared axes, using specific verbs ('overlay') and resource ('plots'). It distinguishes from dashboards by contrasting side-by-side placement with compositing onto a single set of axes, and gives concrete use cases (comparing distributions, model vs actual).

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 explains when to use overlay (comparing on shared axes) versus dashboard (side-by-side), but does not explicitly state when not to use it or mention other alternatives beyond that one comparison.

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