calculate_compound_interest

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

No annotations are provided, so the description carries the burden. It describes the tool as a computation (returns final amount, total interest, yearly breakdown) but does not explicitly state it is read-only or side-effect-free. Since it's a simple calculation, the lack of explicit safety disclosure is a minor gap.

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 very concise, using two sentences to convey purpose, formula, use cases, return values, and a cross-reference. Every sentence adds value without redundancy.

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 (implied by context), the description adequately explains the tool's function and returns. It covers the key use cases and mentions a bundle for related tools, providing sufficient context for a calculator.

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?

The input schema has 100% coverage, meaning all parameters have descriptions. The description adds context by providing the formula and clarifying the return structure, but the schema already defines each parameter adequately. This baseline of 3 is appropriate.

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 computes compound interest growth, provides the formula, and lists use cases like savings and retirement projections. However, it does not differentiate from sibling calculators such as calculate_simple_interest or calculate_future_value, which could cause confusion.

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 explicitly states when to use: for savings, retirement projections, and investment forecasting. It also references list_bundles for related calculators, offering guidance but not excluding alternatives.

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