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

With no annotations, the description carries the behavioral disclosure burden. It does disclose the score scale, percentile, tier, and component breakdown, which helps set expectations. However, it does not mention what happens for invalid or unknown suburb names, data availability, or whether this is purely a read operation.

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, compact sentence that front-loads the core output and then adds supporting detail. Every phrase adds value and there is no redundancy.

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 required string parameter and an output schema, the description is reasonably complete: it names exactly what the result contains once invoked. It lacks usage context, but the output structure is clearly summarized and the parameter list is minimal.

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, has no schema description and the tool description does not mention it at all. There is no guidance on expected format, case sensitivity, aliases, or whether full names or IDs are accepted. With 0% schema coverage, the description fails to compensate.

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 identifies the tool's output: a cultural-integration composite score from 0-100, national percentile, tier, and per-microburb sub-scores. It effectively distinguishes this composite demographic metric from the many sibling demographic tools by naming the specific composite and its components.

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 on when to use this tool versus alternatives such as suburbs_demographics_all, suburbs_ethnicity_all, or other demographic-specific tools. The description does not state context, exclusions, or how this composite relates to sibling options.

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