compound_interest_calculator

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

There are no annotations, so the description carries the full behavioral burden. It discloses the core behavior, the optional monthly contribution, and the compoundFreq default of 12. However, it does not specify the exact return value, whether contributions are applied at the start or end of each period, or how rounding is handled.

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?

Two compact sentences convey the formula scope and all input parameters with no wasted wording. The parameter list is front-loaded and easy to scan.

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?

The definition covers the parameters and a key default, and there is no output schema to document the result. Still, it omits the output format, the default for monthlyContribution, and any usage context, leaving minor but real gaps for an agent.

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 0%, so the description compensates by listing all five parameters, clarifying that annualRate is a percentage, and giving compoundFreq a default of 12. It does not fully explain compoundFreq as 'times per year', but the name and default make the intended meaning inferable.

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 and resource: it calculates compound interest with optional monthly contributions. This clearly differentiates it from the sibling fee, discount, margin, and loan calculators by naming the exact financial operation.

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 intended use is implied by the name and description: use this when compound interest or contribution growth is needed. However, there is no explicit when-to-use or when-not-to-use guidance, nor any mention of alternatives like loan_calculator for amortizing calculations.

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