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

Annotations declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, covering safety and openness. The description adds useful behavioral context about compounding options and notes that most Indian FDs compound quarterly, which helps an agent choose default parameters in a domain-specific way. No contradictions.

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 front-loaded with the purpose, then uses an Args block that is well-structured for a function signature. It is slightly verbose but each sentence adds value, with no wasted words.

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 no output schema, the description could clarify the return value (e.g., whether it returns a number or object). However, it fully covers inputs, safety via annotations, and a domain-specific default recommendation, making it nearly complete for a calculator 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 coverage is 0%, so the description must fully document parameters. It provides clear semantics for each: deposit_amount as principal in rupees, annual_rate as percentage, years as tenure with an example, and compounding with an enumerated list and a domain hint about quarterly compounding.

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 states a specific verb ('Calculate') and resource ('FD maturity amount with compounding'), distinguishing it from siblings like calculate_emi or calculate_sip. An agent can immediately tell this computes fixed deposit maturity.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., find_best_fd or compare_products). While the purpose is clear, the agent must infer usage context without any explicit when/when-not or alternative recommendations.

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