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

The only behavioral claim is 'Expression discarded', which hints at a non-persistent operation but is unexplained and conflicts with the expectation that 'evaluate' produces a result. There are no annotations, so the description carries the full burden of disclosing return values, side effects, and failure modes, and it does not do so.

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 short and front-loaded, but it is under-specified rather than efficiently specified. The cryptic second sentence and the total omission of parameter mapping mean the terseness detracts from usability instead of helping.

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?

For a tool with seven parameters, no output schema, and no annotations, two unrelated sentences are wholly insufficient. An agent has no way to know the expected input, the output, or when to select this tool over its siblings.

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 schema documents each of the seven properties, but none of them represents the arithmetic expression the tool claims to evaluate. The description adds no mapping between its intended input and the actual parameters, leaving an agent unable to determine what to pass.

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 phrase 'Evaluate a+b style arithmetic' gives a surface-level purpose, but 'Expression discarded' makes it unclear whether the tool computes a result or merely validates a shape. The input schema contains no arithmetic expression parameter, so the description does not match the actual schema and does not distinguish this tool from the many sibling shape/check tools.

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 calc-eval versus any alternative. Despite a long list of sibling shape, validation, and fetch tools, the description offers no context, exclusions, or selection criteria.

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