sympy_nsimplify

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

No annotations are provided, so the description must fully disclose behavioral traits. 'Numerical simplification' does not explain whether the tool performs approximation, returns a number, or handles symbolic expressions. It lacks specifics about side effects, permissions, or output behavior.

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 short (two words) without waste, but it is too minimal to be informative. It sacrifices substance for brevity, making it borderline insufficient for guiding an agent.

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 that the tool is part of a comprehensive SymPy suite and an output schema exists, the description should provide enough context for the tool's role. It fails to explain how nsimplify differs from simplify or other tools, and does not clarify the nature of numerical simplification (e.g., converting floats to rationals).

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?

The input schema has one parameter 'expr' with 0% description coverage, and the description adds no meaning beyond the schema. The agent receives no information about what the parameter should contain (e.g., a string representation of a SymPy expression, a number, etc.).

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 'Numerical simplification' indicates a specific action (simplification) and domain (numerical), but it is too terse and does not adequately differentiate from sibling tools like sympy_simplify, which likely performs symbolic simplification. A more specific verb-resource combination would improve clarity.

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 guidance on when to use this tool vs alternatives such as sympy_simplify or other transformation tools. The description implies usage for numerical contexts but offers no explicit when-to-use or when-not-to-use instructions.

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