mathematica_simplify

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

No annotations are provided, so the description must convey behavioral traits. It only states the basic function without disclosing side effects, limitations, or the nature of simplification (e.g., algebraic, symbolic). This leaves significant gaps for an agent.

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, concise sentence, but its brevity sacrifices helpfulness. It is not overly verbose, but it fails to provide enough context to be deemed efficient.

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?

Despite the presence of an output schema, the description is critically incomplete. With 3 parameters, no annotations, and a long list of sibling tools, the description offers no details on return values, parameter usage, or behavioral nuances, leaving a knowledgeable agent underinformed.

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%, meaning parameter descriptions are completely absent from the schema. The tool's description adds no semantic information about the 'expression', 'assumptions', or 'full' parameters, leaving the agent without necessary guidance.

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 'Simplify a mathematical expression' uses a specific verb and resource, clearly indicating the tool's action. However, it lacks differentiation from sibling tools like mathematica_expand or mathematica_factor, which could also be considered simplifications in certain contexts.

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, nor does it mention any prerequisites or exclusions. The agent is left to infer usage without explicit context.

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