mortgage_rates

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

No annotations provided, but description fully discloses cost ($0.02/call), data source (FRED), settlement (Base mainnet), and that it always returns a current snapshot. No side effects or 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?

Three sentences efficiently convey purpose, outputs, and context. No redundant phrases, though could be marginally tighter. Well-structured with front-loaded purpose.

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 zero parameters and no output schema, the description covers all needed context: what rates are returned, cost, source, and that it's a snapshot. No gaps remain for an agent to use the tool correctly.

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?

No parameters exist, and schema coverage is 100%. Description explicitly states 'No parameters required', adding clarity beyond the schema. Baseline 4 for zero params is exceeded by the helpful note.

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 clearly states the tool returns live US mortgage and macro rates, listing specific rates (30-year, 15-year fixed, prime, fed funds, CPI). It distinguishes itself from siblings by focusing on financial rates, with no ambiguity.

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?

Explicitly tells when to use: when user asks about current mortgage rates, refinance rates, prime rate, etc. Although it does not mention when not to use or alternatives, no close sibling tools exist, making the guidance sufficient.

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