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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions operations but does not reveal error handling, behavior on invalid inputs, whether the tool is pure (no side effects), or the effect of the simplify flag. For a calculation tool, this is minimal disclosure.

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 compact sentence, efficient and easy to scan. However, it omits parameter usage and differentiation guidance, so the conciseness comes at the cost of valuable missing information.

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 no annotations, absent parameter descriptions, and a crowded sibling list, the description is incomplete. It fails to clarify when to choose this over compute_number_theory or verify_arithmetic_claim, and does not explain the roles of variables and simplify. The output schema exists, so return values are covered, but calling guidance is lacking.

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 description adds no meaning to the parameters: expression, simplify, and variables. It does not explain how variables are formatted (e.g., as a map) or what simplify changes in the output. The agent is left to guess parameter semantics entirely from titles and types.

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 states a specific verb ('evaluate or simplify') and resource ('mathematical expressions'), and lists supported functions (sqrt, exp, log, sin, cos) and PEMDAS. It is clear, but does not explicitly differentiate from sibling tools like verify_arithmetic_claim or solve_equation_system, though the core purpose is evident.

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?

No guidance is provided on when to use this tool versus alternatives such as cognitive.verify_arithmetic_claim or cognitive.solve_equation_system. There is no when-not-to-use context or mention of prerequisites, leaving the selection entirely to inference from the name.

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