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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so the safety profile is covered. The description adds useful context beyond that: the computation method (I = P × r × t), supported time units, and that it reports the total due. It does not, however, describe the full return shape.

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?

Front-loaded with a concrete worked example followed by the governing formula, which is easy to scan. The trailing webpage URL is low-value for invocation but not enough to disrupt structure.

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 no output schema, the description usefully signals what comes back ('shows the total due'), and annotations cover safety. Combined with fully documented parameters, an agent has what it needs to call the tool correctly.

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 coverage is 100%, so the schema already documents all five parameters, including the unit enum (years/months/days) and currency list. The description reinforces the term units and the role of principal/rate in the formula but adds little syntax or format detail beyond the schema, so the baseline 3 applies.

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 operation (simple interest calculation) and pins down the exact formula I = P × r × t, with a worked example. It implicitly distinguishes itself from compound_interest_calculator via the 'simple' formula, but never names that sibling explicitly, so full differentiation is left 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?

The formula and example imply the tool's domain, but there is no explicit when-to-use vs the adjacent compound_interest_calculator or interest-related calculators. Usage is implied rather than stated.

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