calculate_emi

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

With no annotations, the description carries the full burden. It discloses the return format ('backend JSON payload' or 'error structure') and hints at a 'backend calculation strategy', but does not explicitly state that this is a read-only operation or mention any side effects or permissions. It provides some context but not deep behavioral 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 opens with a clear one-sentence purpose, followed by a well-organized parameter list and a return statement. Every line is informative with no redundancy or filler, making it highly efficient.

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 doesn't need to enumerate return fields. It covers all parameters with units, specifies the return shape, and scopes the tool to single loans. It could be slightly more explicit about the boundary with sibling tools, but it is otherwise complete for a simple calculator.

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?

The input schema has no descriptions for parameters (0% coverage). The description fully compensates by explaining each parameter: principal as loan amount, interestRate as annual percent with an example, tenure in months, and calculation_method as a backend strategy. This adds essential meaning that the schema lacks.

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 uses the specific verb 'calculate' and resource 'EMI', scoped to 'a single loan scenario'. This clearly distinguishes it from sibling tools like compare_loans or calculate_with_prepayment.

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 phrase 'for a single loan scenario' implies the primary use case, but the description does not explicitly list when to use this tool versus alternatives such as calculate_schedule or compare_loans. It offers no 'when not to use' guidance.

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