fraction_calc

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

With no annotations, the description carries full burden. It only states the action and parameters, lacking any disclosure of side effects, error handling (e.g., division by zero), or performance characteristics. Minimal transparency.

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?

Extremely concise: one sentence plus a bullet-like parameter list. Every piece is meaningful, no fluff. Front-loaded with purpose.

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 the presence of an output schema, return values are covered. The description covers operation and parameters well. However, it misses critical constraints like denominator != 0, which is essential for correct use. Slightly incomplete.

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?

Despite 0% schema coverage (no descriptions in JSON schema properties), the tool description provides clear explanations for all 5 parameters, including allowed values for 'operation' and defaults for optional ones. This fully compensates for the schema gap.

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 clearly states the tool performs arithmetic operations on fractions (add, subtract, multiply, divide). The verb 'Perform' and resource 'arithmetic operations on fractions' are specific, and the listed operations distinguish it from siblings like geometry_calc or general math 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?

No guidance on when to use this tool vs alternatives. It does not mention any context, prerequisites, or when not to use it. With many math-related siblings (e.g., evaluate_math, quadratic_solver), this is a gap.

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