HIBOR fixings

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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds valuable behavioral context beyond annotations: the dataset only contains two tenors, and overnight HIBOR can swing around quarter and month ends. This helps the agent set expectations about data coverage and volatility without contradicting the annotations.

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 filler. The key dataset identity is front-loaded, followed by scope limitations and a focused usage tip. Every sentence earns its place.

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?

With an output schema present, no return-value explanation is needed. The description covers the dataset's identity, tenor scope, data caveat, and the value of the history option, which is sufficient for a simple read-only lookup tool.

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 description coverage is 100%, so both parameters are already documented in the schema. The description adds only general context about returning recent history, which maps to history_days, but does not provide additional detail beyond the schema. Baseline 3 is appropriate.

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 identifies the resource (Hong Kong Interbank Offered Rate) and states the tool's behavior: it publishes two specific tenors and optionally returns recent history. It is distinct from siblings like get_base_rate and get_peg_status by naming a different financial rate and dataset scope.

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 gives clear context for when to use the tool: the dataset covers only overnight and one-month tenors, and other tenors are explicitly excluded. It also advises that recent history is where HIBOR is actually informative, guiding use of the optional history parameter. It does not explicitly name sibling alternatives, but the exclusion alone provides useful when-to-use guidance.

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