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

The readOnlyHint and openWorldHint=false annotations already establish this as a safe, closed-domain read, so the description only needs additive context. It does add what the response contains (current rate, last decision date, next meeting), which is valuable given there is no output schema, but says nothing about freshness, rate limits, or coverage of banks/meetings.

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?

A single ten-word sentence that front-loads the resource and then the payload, with zero filler. It is perhaps overly terse given the two parameters, but nothing is wasted.

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 no output schema, the description usefully sketches the return shape, and the annotations cover the safety profile. It remains incomplete for a two-parameter tool: the history parameter's meaning and the multi-bank behavior are left entirely to schema inference, which the agent cannot fully do since history is undocumented.

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 only 50%: the bank parameter is documented in the schema with allowed values and an omit-for-all default, but the history parameter (integer 0-50, default 0) has no description anywhere. The tool description never mentions either parameter, so it does not compensate for the gap — in particular, an agent cannot tell that history requests past decisions.

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 names a specific resource (policy rates) and enumerates the returned fields (last decision date, next meeting), which separates it from snapshot siblings like macro_latest and macro_yield_curve. It does not explicitly name or contrast those siblings, so it stops 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?

"Current" implies a snapshot use case and the schema notes bank can be omitted for all, so the intended usage is inferable. However, there is no explicit when-to-use statement and no alternative tool (e.g., macro_yield_curve for curve data, macro_history for series depth) is referenced.

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