Taux d'intérêt canadiens courants / Current Canadian interest rates

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

No annotations are provided, so the description carries full burden. It discloses that data is read live from Bank of Canada API, each figure has its own observation date, and mortgage figures are system averages, not offers. This gives essential interpretation context.

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?

Four sentences, each adding substantive information: content enumeration, data source, caveat, attribution. No filler.

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 zero-parameter read-only tool, the description covers content, source, freshness, and interpretation caveat. No output schema needed since values are standard interest rates.

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?

Tool has zero parameters, so schema coverage is complete. Baseline 4 applies; description adds no parameter-specific info needed.

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?

Clearly specifies the tool returns current Canadian reference interest rates, listing exact instruments (policy rate, prime, mortgage averages, bond yields). The verb 'Call this for' and specific list distinguish it from sibling real-estate 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?

The description begins with 'Call this for...' and enumerates the exact use case. No alternatives are mentioned, but sibling tools cover other real-estate topics, so the context is unambiguous.

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