Get dated interest rates

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

With no annotations, the description carries the behavioral disclosure burden, but it only states that the tool 'returns' data, which implies a read-only operation. It does not disclose any side effects, authorization requirements, rate limits, or behavior when the requested date has no rates available; still, it is not misleading.

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, front-loaded sentence with no filler or redundant phrasing. Every word contributes to understanding the returned data, and no important structured property is repeated or contradicted.

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 has one parameter and an output schema, the description is minimally viable, but not complete. It fails to clarify the semantic relationship between the 'as_of' parameter and the returned rates' effective dates, and it offers no clue about how this tool relates to the mortgage siblings.

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 schema has 0% description coverage for the only parameter 'as_of', and the description adds almost nothing about how this parameter changes the result. Phrases like 'effective dates' and the title 'Get dated interest rates' hint at date filtering, but the description does not explicitly say whether as_of selects rates effective on, before, or after the given date.

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 says 'Return available rates with effective dates and source metadata,' which is a specific verb plus resource and clearly describes the output. It does not explicitly reference sibling tools, but the focus on dated rates with source metadata is enough to set it apart from mortgage products and calculation tools.

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 guidance about when to choose this tool over siblings such as calculate_mortgage, compare_mortgages, or list_mortgage_products. It does not say what kind of request or scenario best fits this tool, nor does it mention any restrictions or prerequisites such as authorship.

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