plot_multi_expression

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 states plotting behavior ('overlaid on a single 2D graph') but does not disclose side effects, session handling, or error behavior. For a tool with 5 parameters, this is minimal disclosure.

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 a single, front-loaded sentence with no wasted words. It immediately conveys the core functionality.

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 a full input schema and an output schema, the description does not need to explain return values. The short description covers the key behavior, and the schema provides the remaining parameter and default details. It is reasonably complete for a plotting tool, though it lacks usage examples or non-schema context.

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 the baseline is 3. The description adds minimal parameter meaning beyond the schema—it mentions 'multiple expressions' and 'overlaid,' which aligns with the expressions parameter, but does not elaborate on any other parameters. The schema covers the rest.

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 uses a specific verb+resource ('Plot multiple expressions') and clearly states the overlay on a single 2D graph, which effectively distinguishes it from siblings like plot_expression (single expression) and plot3d_expression (3D).

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 implies usage for multiple expressions but does not explicitly state when to use it versus alternatives like plot_expression, nor does it mention exclusions or prerequisites. The 'multiple expressions' wording provides only implicit guidance.

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