calculate_sip_returns

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

The annotations already cover readOnlyHint and isOpenWorldHint, indicating the tool is a safe, deterministic calculation. The description adds that the return is a corpus with wealth gained and inflation-adjusted value, which provides some context, but the description mostly states the mapping rather than exposing new behavioral content like calculation assumptions or response shape. No annotation contradiction.

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 well-structured: a short clear purpose, a usage signal, a preliminary contract, and a return summary. The Args and Returns blocks are slightly redundant with the schema and output schema, but the overall length is appropriate and easy for an agent to parse.

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 this is a deterministic calculation tool with a readOnlyHint, idempotentHint, a complete input schema, and a known output schema, the description is adequate for an agent to select and invoke it correctly. It identifies the domain, lists the core parameters, and indicates what kind of result the caller should expect.

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 input JSON schema fully documents monthly_investment, expected_annual_return, tenure_years, and inflation_rate. The description repeats these parameters but adds little meaningful semantics beyond naming them, and does not clarify edge cases such as sign, currency, or validation beyond the schema's existing descriptions.

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's purpose: calculating SIP maturity with inflation-adjusted returns, with a specific mention of mutual fund SIP and systematic investment planning. However, within a large family of investment calculators, it does not explicitly differentiate itself from siblings like calculate_step_up_sip or calculate_ppf_maturity, though the focus on SIP and inflation-adjustment gives reasonable clarity.

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 says when to use the tool: when projecting mutual fund SIP returns or planning systematic investments. It provides a clear usage context but does not state when it should not be used or which sibling alternatives might be more appropriate for step-up SIP, PPF, FD, or RD calculations.

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