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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that — a cost of 2 credits — plus the composite-rate composition, but it omits how far back historical data goes, how frequently rates are refreshed, and whether missing periods return errors or empty results.

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 opening 'I-Bond Rates: I-Bond Rates' duplicates the title and name with zero information gain. The middle sentence explaining fixed-plus-inflation composite rates is useful domain context for interpreting results, but the credit-cost note is appended awkwardly in parentheses rather than integrated.

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?

For a one-optional-parameter lookup with an output schema, the definition covers purpose, instrument definition, and cost, which is enough for an agent to call it correctly. The remaining gap — historical depth and refresh cadence — is a nice-to-have rather than something that would cause a misinvocation.

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 100% and the single optional 'period' parameter is fully documented in the schema, including the YYYY-MM format and the omit-for-current behavior, so the baseline is 3. The description's 'current and historical' phrasing reinforces the parameter's purpose but adds no format or edge-case detail beyond the schema.

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 and resource ('provides current and historical interest rates for US Series I Savings Bonds') and names the exact instrument, so an agent can distinguish it from generic rate tools. It does not explicitly contrast itself with close siblings such as TreasuryYields, InterestRate, or InflationRate, which keeps it short of a 5.

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?

There is no when-to-use guidance, no exclusions, and no named alternative among the many rate-related siblings. The only selection cue ('Omit for current rates') lives in the schema, not the description, and the note that rates adjust every 6 months is domain background rather than invocation guidance.

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