plot_over_line

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

The description discloses key behavioral aspects: it samples along a line and returns coordinate arrays and field values. However, it does not mention whether the tool is read-only or if it has side effects like creating a plot. With no annotations, the description partially informs but leaves ambiguity about mutability.

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 long, front-loaded with the core action, and contains no superfluous information. Every word contributes to clarifying the tool's function.

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, the description does not need to detail return values, but it still mentions 'Returns coordinate arrays and field values for plotting,' which is helpful. It covers the essential purpose and a hint about output, but could be more explicit about default resolution or timestep handling.

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 description adds context about returning coordinate arrays and field values for plotting, which helps understand the purpose but does not add specific meaning beyond what the input schema provides. Since schema coverage is 100%, the baseline of 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?

Clearly states that the tool samples field values along a line between two points and returns data for plotting. It names the resource (field values) and action (sample), making the purpose obvious. However, it does not explicitly differentiate from sibling tools like 'probe_timeseries' or 'extract_stats'.

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 such as 'probe_timeseries' for point sampling or 'slice' for planar sampling. There is no mention of prerequisites, use cases, or when not to use the tool.

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