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

With no annotations, the description carries the full behavioral disclosure burden. It clearly states that values are predicted incidents per 100,000 residents per year and points to the payload's unit/definition keys, making the output semantics transparent. It does not discuss side effects, but for a data-retrieval tool the value interpretation is the critical context.

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 two compact sentences with no filler. The first sentence front-loads the resource and granularity; the second adds essential unit semantics. Every clause earns its place.

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?

The presence of an output schema covers return-value structure, and the description supplies the key output semantics: predicted incidents, per-100k rate, and ABS mesh-block keying. For a one-parameter read-oriented tool, this is nearly complete; only explicit alternative routing is missing.

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%, so the description must compensate. It ties the lone suburb_name parameter to 'the suburb' being queried, which is helpful, but it does not explain accepted name formats or how to disambiguate similarly named suburbs. The single intuitive string parameter makes this adequate but not thorough.

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 resource: total crime rate per mesh block within a suburb, keyed by ABS mesh-block code. It is specific enough to distinguish this from the sibling suburbs_crime_summary and suburbs_crime_breakdown tools by emphasizing mesh-block-level granularity.

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?

The intended use is implied: call this when you need mesh-block-level crime rates for a suburb. However, it does not explicitly compare itself to suburbs_crime_summary or suburbs_crime_breakdown, nor does it state when a coarser or finer crime tool should be chosen instead.

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