harmonic_series

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

No annotations are provided, so the description carries the full burden. It does disclose the exact computation (a deterministic, side-effect-free formula), but says nothing about behavior for out-of-range n, floating-point precision/overflow for large n, or that it grows logarithmically rather than converging.

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 with the formula appended; no filler, nothing redundant.

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 single-parameter pure calculation with full schema coverage and no output schema, the definition supplies everything needed to call it correctly. Only edge-case/range behavior is unaddressed, which is a minor gap.

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% and the single parameter n is documented in the schema with its 1-100000 range, so the description adds no parameter detail beyond restating n in the formula. Baseline 3 is appropriate when the schema does the work.

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 verb (calculate) and resource (partial sum of the harmonic series), and spells out the formula H(n) = 1 + 1/2 + ... + 1/n, so an agent knows exactly what is computed. It does not differentiate from nearby siblings such as geometric_series, but the formula makes the operation unambiguous.

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 or which alternative applies; the description is purely definitional. For a pure math helper that may be acceptable, but no usage guidance is offered at all.

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