solve_symbolic_equation

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

With no annotations, the description carries the full burden, and it does disclose two useful behavioral details: bare expressions are assumed equal to zero, and output is a list of solution strings (shown via example). It is silent on the solution domain (real vs. complex), multiple/no solutions, and error behavior, which is a meaningful gap for an unannotated math tool.

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?

Two short sentences with the core purpose and a worked example front-loaded, and the accepted-input-forms note following. No filler; every clause adds information.

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?

An output schema exists, so return values need not be re-explained, and the example conveniently previews them. However, with zero schema description coverage, no annotations, and an undescribed variable parameter, the description leaves gaps an agent would want filled before calling correctly.

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 0%, so the description must compensate. It adds real meaning for the required equation parameter (bare expression vs. explicit '=' form) plus a worked example, but says nothing about the variable parameter, including that it defaults to 'x' and how it selects the solved-for variable.

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+resource ("Solve an equation for a variable") and reinforces it with a concrete example mapping an input equation to its solution set. It clearly differs from computation siblings like evaluate, but it never distinguishes itself from solve_quadratic or solve_linear_system, which plausibly overlap.

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?

There is no explicit when-to-use guidance and no mention of alternatives such as solve_quadratic or solve_linear_system, which are the natural siblings an agent would confuse this with. The note about bare expressions describes input format, not when this tool should be selected over others.

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