mathematica_solve

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

No annotations are provided, so the full burden is on the description. The description only states that it solves an equation, but does not disclose side effects, return format (though output schema exists, its content is not described), required prerequisites, or limitations. The agent is left uninformed about behavior beyond the basic operation.

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 extremely concise (6 words) but at the cost of missing essential information. While brevity is valued, it should not sacrifice necessary context. A few additional sentences clarifying parameters and usage would improve utility without excessive verbosity.

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 absence of annotations and low schema coverage, the description is incomplete. It does not leverage the output schema (which exists) to clarify return values, nor does it address the complexity of solving equations. Sibling tools suggest a rich ecosystem, and more context about when to use this specific tool is needed.

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%, and the tool description adds no meaning for any of the three parameters. The text does not explain that 'equation' is the mathematical expression, 'variable' is the unknown to solve for, or 'domain' restricts solutions. Without any guidance, the agent must infer parameter semantics from names alone.

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 'Solve an equation using Solve' clearly states the verb (solve) and resource (equation). It distinguishes the tool from siblings like mathematica_integrate or mathematica_factor by focusing on solving equations. However, it does not specify the type of equations (e.g., algebraic, differential) or the scope of Solve.

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 alternatives. Sibling tools include mathematica_simplify, mathematica_expand, etc., but no comparison or context is given. An agent cannot determine when solving versus simplifying or factoring is appropriate.

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