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

No annotations are provided, and the description contains zero behavioral disclosure. It doesn't mention response size, performance characteristics, error handling, or any side effects. With no annotations to cover the safety or behavior profile, the description fails to provide any transparency.

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 extremely brief, but this is not concise—it's under-specified. It consists of a fragment 'All ethnicity — bundle' with no structure or elaboration. It lacks any meaningful content that would help an agent understand the tool.

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 bundle tool with only one parameter, the description is severely incomplete. It doesn't hint at what the bundle contains, how the data is organized, or what the output schema provides. The presence of an output schema is not enough; the description should explain what the tool returns. An agent would be completely in the dark about the tool's capabilities.

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 only parameter, suburb_name, is a simple string whose meaning is obvious from its name. However, with 0% schema description coverage, the description should add context or constraints, but it doesn't mention the parameter at all. The description provides no additional semantic value beyond the parameter name.

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 'All ethnicity — bundle' is extremely vague. It doesn't specify what data is included (e.g., ancestry, birthplace, cultural integration) or what the tool actually returns. It fails to differentiate from sibling tools like suburbs_ethnicity_ancestry and suburbs_ethnicity_birthplace, leaving the agent without a clear understanding of the tool's specific purpose.

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 the specific ethnicity tools (ancestry, birthplace, etc.). No mention of alternatives, prerequisites, or any decision criteria for selection. The agent has no basis to choose this over its more specific siblings.

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