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

No annotations are provided, so the description carries the full burden. It lists the fields returned but does not disclose whether the tool requires an exact suburb name, whether it returns a single record or multiple matches, or what happens for ambiguous or unknown suburbs. The output schema exists but the description adds no behavioral context beyond the field list.

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 a single concise sentence that front-loads the key output fields. It is efficient, though it could add a brief usage note without becoming bloated.

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?

Given the tool has one parameter, an output schema, and a simple summary purpose, the description is close to adequate but misses critical input-format guidance and behavior for ambiguous inputs. The output schema covers return values, so the main gap is input semantics and edge-case behavior.

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% and the only parameter, suburb_name, has no description in the schema. The tool description does not explain what format the suburb name should take (e.g., 'Sydney' vs 'Sydney NSW'), case sensitivity, or whether it accepts postcodes. With zero coverage and no compensation, the parameter semantics are under-specified.

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 states a clear verb and resource: it returns a summary of core suburb attributes (State, SA3/SA4, postcode, population, dwellings, centroid). It is distinguishable from siblings like suburbs_profile or suburbs_list, though it doesn't explicitly name an alternative.

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?

No guidance on when to use this tool versus the many other suburbs_* tools. The description implies it is a quick summary/hero endpoint, but it doesn't state that explicitly or mention alternatives.

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