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

There are no annotations, so the description carries the transparency burden. It does disclose the data source and general output type, which is useful for a simple read-only lookup. However, it does not mention output format, limitations, or any suburb-name handling nuances.

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 focused sentence with no filler and the key term 'Ancestry breakdown' is front-loaded. It is concise, though the brevity leaves some contextual gaps captured by other dimensions.

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 single-parameter tool with an output schema, the description is minimally adequate: it names the resource and source. But given the dense field of similar ethnicity and demographics tools, an agent may not be fully equipped to distinguish this tool from its siblings without more explicit context.

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 description does not explain the suburb_name parameter. The parameter name is self-explanatory, but no additional semantic context is added to compensate for the missing schema description.

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 names the output ('Ancestry breakdown') and the data source ('ABS census'), which makes the tool's purpose reasonably clear. It does not explicitly frame the action with a verb or contrast itself with suburbs_ethnicity_all or suburbs_ethnicity_birthplace, but the core resource is identifiable.

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 is given about when to use this tool versus the many related sibling tools, especially suburbs_ethnicity_all, suburbs_ethnicity_birthplace, and suburbs_demographics_ancestry_map. The tool name provides some hint, but the description itself offers no selection criteria or exclusions.

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