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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered structurally. The description contributes nothing beyond that — 'client and server side' is opaque and does not describe computation behavior, rounding, or output 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?

It is a single short sentence, which is appropriately sized, but a meaningful fraction of it ('client and server side from freedailypro') is wasted marketing text rather than the parameter or usage detail the agent needs.

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 and only 25% parameter coverage, the description should explain what the tool returns (interest amount? total?) and how startDate/maturityDate affect results. It supplies none of this, leaving the agent to guess at the return value for a 4-parameter calculation tool.

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 only 25% — only startDate is documented (and its note about labeling the timeline is genuinely helpful). The description itself explains none of principal, annualRatePercent, or years, and does not clarify the 0-100 bounds or the exclusiveMinimum constraints, so it fails to compensate for the coverage gap.

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 phrase 'Simple interest calculator' does name a specific verb+resource, so the core purpose is recoverable. But 'client and server side from freedailypro' is unexplained noise that adds no discriminating information, and nothing distinguishes it from sibling calculate_compound_interest or calculate_loan.

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 when-to-use guidance at all: no statement of when simple interest applies versus compound interest, no prerequisites, no exclusions. The agent must infer selection purely from the tool name.

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