plot_function

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

No annotations present, and the description fails to disclose any behavioral traits such as output format (e.g., rendered image), side effects, or error handling. The sole sentence says nothing beyond the basic action.

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 sentence, which is concise but severely under-specified. It lacks necessary detail, making it insufficient for an agent to use the tool correctly.

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 complexity of 10 parameters, no annotations, and an output schema not described, the description is completely inadequate. It fails to provide essential context for parameter usage, output expectations, or typical use 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?

With 0% schema description coverage and 10 parameters, the description adds no meaning to any parameter. It does not explain the required 'expression' parameter, its acceptable formats, or optional parameters like 'x_range' or 'num_points'.

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 states the tool plots functions as 2D curves, which is clear. However, it does not explicitly differentiate from sibling tool 'plot_implicit' for implicit plots, missing an opportunity for specificity.

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 on when to use this tool vs alternatives like 'plot_implicit'. No exclusions or context provided.

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