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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes beyond that by disclosing the return shape (`{lga, state}` per row) and the billing model (flat 1¢ per call). That cost transparency is the kind of context an agent cannot get from structured fields. It stops short of a 5 only because it omits result volume and any behaviour for an invalid state value.

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?

Extremely compact and front-loaded: purpose first, filter second, return shape third, cost last. The only minor waste is the near-duplication of 'Flat cost' and 'Price: 1¢ per call', though the pairing does clarify flat-per-call versus per-row billing.

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-required-parameter enumeration tool with no output schema, the description plus annotations cover everything needed to call it correctly: scope, filter, return fields, and price. The remaining gap is modest — no mention of roughly how many rows (~540) or whether an unrecognised state yields empty results or an error, which would help set agent expectations on cost and output size.

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 100% and the single `state` parameter is fully documented in the schema, including example values, so the baseline is 3. The description's `?state=` notation and '(e.g. NSW)' duplicate rather than extend the schema's meaning.

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 a specific verb and resource ('All Australian LGAs'), so the agent immediately knows this is a full enumeration of LGA entities. It does not differentiate from related siblings such as lga_profile, lga_population, or the parallel list tools (suburbs_list, sa4_list, mbs_list), which is why it falls 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?

Usage is only implied: the word 'All' signals enumeration and the optional state filter hints at narrowing. There is no explicit guidance on when to use this versus lga_profile for a single LGA's details or sa4_list/suburbs_list for other geographies, and no stated prerequisites.

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