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

No annotations are provided, so the description must fully disclose behavior. It only says 'Expression discarded,' but no expression input exists, and it does not mention outputs, side effects, or side-effect-free guarantees.

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 and front-loaded, but it omits essential information about the missing expression parameter and the role of the schema parameters. It is concise but not usefully structured.

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?

With no required parameters, no output schema, and a description that does not connect the schema to the stated operation, the tool is contextually incomplete. An agent cannot determine expected inputs, outputs, or side effects.

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?

All nine parameters are optional and have descriptions seemingly copied from unrelated tools (e.g., 'Git ref name', 'HTTPS URL to normalize or cite'). The description does not explain how any of these parameters relate to arithmetic evaluation.

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 action ('Evaluate a+b style arithmetic') and resource, which appears distinct from sibling tools. However, the input schema contains no expression parameter, making the stated purpose unimplementable and unclear.

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 provides no guidance on when to use this tool versus alternatives, nor any conditions, prerequisites, or examples. It is impossible to know how to invoke it correctly.

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