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

Annotations already declare this a safe, idempotent, read-only, non-open-world computation, so the safety profile is covered. The description adds useful context by giving the exact formula and the return contents (final amount, total interest, yearly breakdown). It remains silent on rounding precision, rate-input format assumptions, and edge cases, so it adds moderate but not rich behavioral value.

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?

Three tight sentences with the operation and formula front-loaded, followed by use cases and a bundle cross-reference. No filler, though it could be marginally tighter.

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 an output schema present the description needn't spell out return fields, and it already summarizes them; annotations cover the safety profile. Adding the formula and use cases makes it largely complete for a stateless math calculator, with only precision/edge-case behavior left unstated.

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 schema already documents principal, annual_rate, years, and compounds_per_year; per the rubric this is a baseline 3. The formula A=P(1+r/n)^(nt) loosely signals the roles of n and t but adds no format or unit detail beyond the schema.

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 gives a precise verb+resource ('compute compound interest growth') and even states the formula A=P(1+r/n)^(nt), which cleanly separates it from simple-interest and present/future-value siblings. It stops short of a 5 because it never explicitly differentiates from the very close sibling calculate_compound_interest_monthly, leaving that distinction to inference.

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?

It names concrete scenarios ('savings, retirement projections, investment forecasting') that clearly frame when to reach for this tool, and points to list_bundles for related finance calculators. It does not state when-not to use it or name the obvious alternatives (calculate_simple_interest, calculate_compound_interest_monthly), so it falls short of an explicit routing rule.

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