calculate_bond_duration

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

No annotations provided, so description bears full burden. It mentions what is calculated but not assumptions (e.g., periodic compounding, standard bond structure). Does not disclose that it returns both duration values.

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?

Three concise sentences with no redundancy. Clear and front-loaded.

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 output schema exists, return values are covered. However, lacks context on bond type (standard coupon bond) and no mention of zero-coupon bond handling (separate tool exists). Adequate but not thorough.

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%, yet description adds no parameter explanations beyond what is obvious. Parameters like face_value, coupon_rate, ytm, coupon_frequency are not described.

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 it calculates Macaulay Duration and Modified Duration, which is a specific verb+resource. It differentiates from sibling bond tools like calculate_bond_price, calculate_ytm, etc.

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?

Usage is implied: use when duration is needed. But no explicit guidance on when to use vs alternatives (e.g., convexity for higher-order sensitivity), nor prerequisites like bond type assumptions.

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