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

With no annotations, the description must carry the full burden of behavioral disclosure. It provides none—no mention of what data is returned, whether it is a read-only operation, any side effects, or response format. It is just a fragment with no behavioral information.

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 brief, but brevity here is under-specification rather than conciseness. It lacks essential details about purpose and usage. While there is no fluff, the content is so minimal that it fails to serve its function, making it under-specified rather than appropriately concise.

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 likely aggregates age and income data for a suburb, and given the extensive sibling toolset, the description is grossly incomplete. It does not describe the data coverage, output structure (despite an output schema), or how it differs from individual demographic tools. An agent cannot reliably use this tool based on the description alone.

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 coverage is 0%, so the description must compensate by explaining the sole parameter 'suburb_name'. It does not mention it at all. The parameter is somewhat self-evident from the tool name, but the description adds no meaning or format guidance, failing to compensate for the schema gap.

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 'Age + income — bundle' is a vague label rather than a clear statement of the tool's function. It does not explicitly say it returns demographic data for a suburb, nor does it differentiate from sibling tools like suburbs_demographics_age and suburbs_demographics_income. The name suggests 'all' but the description narrows to age and income, creating ambiguity.

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 separate age, income, or other demographic tools. Given the large sibling list, an agent has no basis to decide whether to call this bundle or a more specific tool. No context or exclusions are provided.

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