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

With no annotations, the description carries the behavioral burden and does usefully disclose the per-row return fields and the flat 3¢ pricing. However, it says nothing about ordering, pagination/limits, sorting, error behavior, or whether any authentication/rate-limit constraints apply, so the transparency is partial.

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 compact: purpose, optional filter, return shape, and cost are each stated once, front-loaded, with no filler. The cost is highlighted as a separate line, which is useful but not redundant.

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 simple single-parameter list endpoint with an output schema, this is nearly complete: it states the scope, the optional filter, the row fields, and the cost. It could be slightly stronger by noting the default no-filter behavior and whether results are sorted, but those are readily inferred from 'All Australian LGAs.'

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 schema already documents the `state` parameter at 100% coverage, so baseline is 3. The description's mention of an optional `?state=` filter with NSW as an example adds no meaning beyond the schema; it only restates what is already there.

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 opens with 'All Australian LGAs' and specifies the return shape `{lga, state}` per row, so an agent can tell this is a list/dictionary tool. It doesn't explicitly differentiate from sibling tools like lga_profile or the various *_list endpoints, but the scope (all LGAs, optional state filter) is unambiguous enough.

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 description implies when to call it: when a list of all or state-filtered LGAs is needed. It does not explicitly state when not to use it or point to alternatives such as lga_profile for detailed LGA data, leaving the selection largely to inference.

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