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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explains the output composition but does not clarify how 'flagged' is determined, whether values are modeled or point-in-time, or any edge-case/error behavior. This is a meaningful gap for a tool with zero annotation coverage.

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 dense sentence with no filler or repetition. It front-loads the core output type (counts and shares) and lists the hazard categories compactly. However, the phrasing is slightly awkward and could be improved with an explicit verb like 'Returns' or 'Provides'.

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 tool is simple with one required parameter and an output schema, so invocation is relatively straightforward. Still, the description does not help an agent distinguish it from similar-sounding siblings like suburbs_risks_counts or suburbs_risks_all, and the lack of behavioral context limits overall completeness.

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 schema has 0% description coverage, and the only parameter is suburb_name. The description indirectly clarifies that the parameter refers to a suburb whose properties are being summarized, but it does not specify acceptable formats, aliases, or constraints. It adds some meaning but leaves the agent to infer most parameter semantics from the parameter name alone.

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 resource: counts and shares of a suburb's properties flagged for six specific hazard types. It is unambiguous about what the tool provides, though it reads as a noun phrase rather than an explicit verb+resource statement, and it does not directly name sibling tools to distinguish itself.

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: an agent needing aggregate bushfire/flood/mine-subsidence/contamination/aircraft-noise/acid-sulfate hazard counts for a suburb would select this tool. However, there is no explicit when-to-use guidance, no mention of alternatives such as suburbs_risks_counts, and no exclusion criteria.

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