plot_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 of disclosing behavioral traits. It does mention the return format (base64 PNG), but it omits important details such as whether the plot is 2D-only, whether it has side effects, what syntax is expected for the expression, or how default ranges are applied.

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, well-front-loaded sentence with no wasted words. It is concise and easy to parse, fulfilling the conciseness dimension even though it is under-specified in other areas.

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?

Although the schema covers parameters and an output schema exists, the description lacks usage guidance and behavioral transparency. Given the sibling tools for 3D and multi-expression plotting, the agent cannot determine when to select this tool, making the description incomplete for effective tool selection.

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 schema provides descriptions for all four parameters (100% coverage), so the description does not need to repeat them. The tool-level description adds the output format context but no additional meaning about parameters. The baseline of 3 is appropriate given the high schema coverage.

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's function with a specific verb ('plot') and resource ('expression'), and adds the output format (base64-encoded PNG). It is unambiguous, but it does not explicitly differentiate from sibling tools like plot3d_expression or plot_multi_expression, which also plot expressions.

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 provides no guidance on when to use this tool versus the available alternatives. It is purely declarative, with no mention of context, prerequisites, or exclusions, leaving the agent to infer usage from the name and sibling list.

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