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

With no annotations, the description carries the full burden, and it does disclose two useful traits: zero cost ('FREE') and freshness ('Latest'). However, it does not say whether this returns a single row or a set, what the 'summary columns' actually contain, or anything about data currency beyond 'latest'.

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?

Two compact fragments with the cost signal front-loaded and no wasted prose. The terseness borders on cryptic ('expenditure-group row'), but every token carries information.

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 with no output schema, the description should say what the returned row covers; 'summary columns' is a gesture rather than an explanation. Given the low complexity this is adequate but leaves the agent guessing about the payload.

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 the baseline is 4; there is nothing for the description to disambiguate. The phrase 'summary columns' loosely frames the output shape but no parameter semantics are 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?

States the specific resource (RBA inflation expenditure-group row) and qualifies it as the latest snapshot with summary columns, which implicitly separates it from the fuller inflation_full_latest. It stops short of naming a sibling explicitly, and 'expenditure-group row' is domain jargon an agent may not resolve without the schema.

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 leading 'FREE' token signals a cost-based selection rationale, and 'Latest' implies a snapshot use case, but there is no explicit when-to-use or when-not-to-use guidance relative to inflation_group or inflation_full_latest. Usage must be inferred.

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