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

Annotations already declare readOnlyHint=true, openWorldHint=false, and idempotentHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the accepted operand syntax (mixed numbers like '2 3/8') and the exact shape of the result (lowest terms, mixed number, decimal, worked steps), which tells the agent what it will get back.

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?

One front-loaded sentence carries the operation, the input syntax, and the three output forms with no filler. The trailing web-page URL is mildly promotional but costs almost nothing.

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 output schema, the description correctly takes on the burden of describing return values and does so explicitly. It stops short of covering edge cases such as invalid input or division by zero, but nothing essential for a correct call is missing.

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 baseline is 3, but the description goes beyond the bare schema labels 'First fraction'/'Second fraction'/'Operation' by demonstrating the accepted string format, including mixed-number input, which the schema does not convey.

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?

States a specific operation (fraction arithmetic with mixed-number operands) and the exact output forms: lowest terms, mixed number, decimal, and common-denominator steps. No sibling tool performs this function, so it is implicitly distinct, but the description never names an alternative the way the highest-scoring definitions do.

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 statement of when to use this tool versus alternatives such as scientific_calculator, percentage_calculator, or ratio_calculator, and no exclusions or prerequisites. The input examples hint at the domain but give no routing guidance.

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