calculate_expression

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

With no annotations provided, the description must carry the full burden of behavioral disclosure, but it only restates the core action. It does not mention side effects, safety implications (e.g., arbitrary code execution), or what happens on invalid expressions, offering no insight beyond the basic purpose.

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 that expresses the essential action and output format without unnecessary words. While it could include more context, it is efficiently structured and front-loaded with the primary verb and object.

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 and a simple parameter, the description lacks contextual completeness. It does not explain how this tool relates to siblings like evaluate_sage or evaluate_sage_streaming, nor does it provide any usage or behavioral context, leaving the agent with an incomplete picture for tool selection and invocation.

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% for the single parameter, as the parameter description mirrors the tool description ('SageMath expression to evaluate'). The tool description adds no extra meaning, but the baseline of 3 is appropriate when the schema already fully documents the parameter.

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 uses a specific verb ('Evaluate') and resource ('SageMath expression'), clearly stating the tool's action. However, it does not distinguish this from sibling tools like evaluate_sage or evaluate_sage_streaming, which may perform similar evaluations.

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 versus alternatives. The description offers no context about suitable scenarios, prerequisites, or exclusions, leaving the agent without direction on choosing this over similar siblings.

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