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

No annotations are provided, so the description carries the full disclosure burden. It usefully reveals that the value is an average aggregated at LGA level, but it does not cover units/currency, missing-suburb behavior, or edge cases such as suburbs spanning multiple LGAs.

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 description is one short sentence with the core metric front-loaded. Every word contributes meaning, and there is no filler or repetition of the input schema.

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 one-parameter lookup with an output schema present, the description is close to complete: it specifies the input and the precise metric returned. Minor omissions such as units and LGA-mapping caveats are not enough to make the tool hard to invoke correctly.

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 0%, so the description must compensate. It adds key context: suburb_name identifies a suburb whose containing LGA is the basis for the rate. It does not give format/casing guidance or an example, but for a single obvious string parameter it is minimally adequate.

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 identifies a specific metric (average annual residential council rate) and its geographic scope (the suburb's LGA), so it goes beyond a tautology of the tool name. It does not explicitly contrast with related siblings like suburbs_development_council_intelligence, so it does not earn 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?

There is no guidance about when to use this tool versus alternatives. The sibling list contains several potentially overlapping rate/development endpoints, but the description does not name any alternative or state a selection condition.

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