renderLtspicePlotImage

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

With no annotations, the description must fully convey behavior. It mentions the output type and core features (run_id resolution, step filtering, pane layout), but omits critical details like defaults for many parameters, limitations (e.g., max points), or side effects. Significant behavioral gaps remain.

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 with the main purpose and key features. However, it could be slightly more structured (e.g., grouping options). No wasted 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 23 parameters, no output schema, and no annotations, the description is incomplete. It covers only a fraction of the parameter semantics and lacks details on return format, error conditions, or performance. The agent would need to infer most behavior.

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 0% (no descriptions in schema), so the description must compensate. It only explains pane_layout, run_id, and step filtering, leaving 20+ parameters (e.g., mode, y_mode, width, height) completely unexplained. Minimal value added beyond parameter names and types.

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 verb 'Render' and the resource 'vectors from a RAW dataset to a plot image'. It distinguishes from siblings like renderLtspicePlotPresetImage (which uses presets) and renderLtspiceSchematicImage (which renders schematics, not plots).

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 hints at usage by mentioning supports for run_id/raw_path resolution and step filtering, but does not explicitly state when to use this tool over alternatives. No exclusions or conditional guidance are provided.

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