symbolic_solve

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

With no annotations, the description must carry the full behavioral burden but discloses little beyond the symbolic nature. It omits assumptions, domain restrictions, return format, error handling, and whether it supports inequalities or only equalities.

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?

One clear, front-loaded sentence with no fluff. However, the extreme brevity leaves gaps that other dimensions penalize; within this dimension, it is appropriately concise.

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?

For a tool with two required parameters, no schema descriptions, no output schema, and no annotations, the description is insufficient. It lacks essential context about input formatting, output, and when to choose it over similar solvers.

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 coverage is 0% and the description does not explain the format or expected content for either parameter. It only says 'for the given variables,' which does not clarify how equations or variables should be represented (e.g., strings, lists, equation syntax).

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?

States a specific verb ('Solve') and resource ('equation or system of equations') with the key qualifier 'symbolically,' which is important for distinguishing from numerical solvers. However, it does not differentiate from sibling tools like symbolic_calculus or symbolic_evaluate, leaving the agent to infer the boundary.

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 explicit indication of when to use this tool versus alternatives such as find_roots, symbolic_calculus, or dsolve_ode. The only usage hint is that it handles one equation or a system, but there is no when-not guidance or prerequisite information.

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