calculate_expression

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

With no annotations provided, the description must fully disclose behavioral traits. It states the output format (numeric/string) but fails to mention whether evaluation mutates session state, requires authentication, or has other side effects. The 'session' parameter implies statefulness, but this is not addressed.

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 sentence with no unnecessary words or repetition. It is front-loaded with the action and outcome, making it highly concise and easy to parse.

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?

The tool is relatively simple with two parameters and an output schema exists, so return details are not needed. However, given the large set of sibling tools, the lack of any usage context or differentiation makes the description only minimally sufficient for disambiguation.

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 100%, so the schema fully documents both parameters. The description does not add any meaning beyond what the schema already provides, such as expression syntax or session behavior, so the baseline score of 3 applies.

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 clearly states the tool evaluates a SageMath expression and returns numeric/string forms, providing a specific verb and resource. However, it does not distinguish this from sibling tools like 'evaluate_sage' or 'evaluate_sage_streaming', which likely perform similar evaluation tasks.

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 offers no guidance on when to use this tool versus alternatives such as simplify_expression, solve_equation, or evaluate_sage. No context or exclusion criteria are provided, leaving the agent to guess based on the generic name.

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