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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It states the data source (ABS census) but does not specify the output format (e.g., counts, percentages, groupings), whether it returns a list or aggregate, or any limitations (e.g., data freshness, geographic scope). This minimal disclosure leaves the agent guessing about the tool's behavior.

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 sentence with no filler words, making it highly concise. It front-loads the core functionality. However, it is so brief that it sacrifices completeness, which is a sign of under-specification rather than ideal conciseness. Still, it earns a 4 for being succinct and to the point.

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 tool with one parameter and an output schema, the description is incomplete. It does not explain the structure of the response, whether it includes percentages, counts, or sorted rankings, or any caveats about data coverage. With numerous sibling tools covering demographics, an agent needs more context to know exactly what this tool returns and when to call it. The presence of an output schema is unknown to the agent, and the description does not fill that gap.

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 single parameter, suburb_name, is not described in the schema or the tool description. Since schema description coverage is 0%, the description needed to clarify the parameter's expected format or constraints, but it does not. The parameter name is self-explanatory to a degree, but the description adds no extra meaning, so it falls short of the required compensation.

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 clearly states the tool provides a 'Country-of-birth breakdown' for a suburb, sourced from ABS census data. This identifies the primary action and resource. However, it does not differentiate this tool from sibling tools like suburbs_ethnicity_ancestry or suburbs_ethnicity_all, which may also provide ethnic or ancestry breakdowns, so it lacks sibling distinction.

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 on when to use this tool versus alternatives. The description does not mention any conditions, exclusions, or comparisons to siblings. An agent would have to infer from the name alone that this is specific to birthplace versus other ethnicity breakdowns, and no context is provided for selecting it over other ethnicity or demographic tools.

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