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

Annotations already cover read-only, idempotent, non-destructive, and closed-world status, so the description earns credit for what they don't say: the per-call price (1¢) and the RBA attribution obligation embedded in the response. Those are real operational facts an agent needs before calling. It stops short of noting caching or freshness guarantees.

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 core sentence is front-loaded and tight, but the second sentence is meta-commentary about RBA terms and attribution that does little to help invocation. The price line is short and earns its place; the licensing sentence is padding.

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 no-parameter, read-only single-value tool with no output schema, the description enumerates the returned fields (target, effective date, last move) and the cost, which is nearly everything needed. Only freshness/caching behavior is left unstated.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly does not invent parameter-style details.

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?

First sentence names a specific verb-less but precise resource and its fields: the RBA's current cash rate target, its effective date, and the last move. That lets an agent distinguish this from economics_cash_rate_series or economics_series, though it never names those siblings explicitly.

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 word 'current' implies a latest-value lookup versus the historical series sibling, but the description gives no explicit when-to-use, when-not-to-use, or alternative routing. With economics_cash_rate_series and economics_series both present, an agent must infer the split from the name alone.

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