calculate_nsc

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

With no annotations, the description carries full burden. It discloses that it handles lump-sum, interest reinvested, annual compounding, and typical 5-year tenure. However, it does not mention edge cases (e.g., zero years, negative principal) or output rounding, though the presence of an output schema mitigates some lack of detail.

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 a single sentence that efficiently conveys the tool's essence: 'NSC maturity' followed by key details. Every word adds value, and the structure is front-loaded with the core purpose.

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 tool's low complexity and the presence of an output schema, the description is adequate but could be more complete. It does not specify the return value format (e.g., maturity amount vs. interest breakdown), and it lacks references to the Indian context. However, it covers the main mechanics.

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 0%, and the description does not elaborate on parameters. While parameter names (principal, years, annual_rate) are clear, the description omits units (e.g., annual_rate as percentage vs decimal). This creates ambiguity, especially since the default is 7.7 (likely percentage).

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 NSC maturity, with specifics on lump-sum, reinvested interest, annual compounding, and typical 5-year tenure. It distinguishes from siblings by explicitly naming 'NSC', a unique Indian savings scheme.

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 implies use for NSC maturity calculation but provides no explicit guidance on when to use this tool versus alternatives like calculate_future_value or other small-savings scheme calculators. No exclusions or prerequisites are mentioned.

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