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

There are no annotations, so the description carries the full behavioral burden. It does add the pricing constraint ('Price: 2¢ per call') and indicates a geospatial proximity scope ('near the parcel'), which are useful. However, it does not state whether the operation is read-only, what the overlay contains, or how the response behaves.

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 very short and front-loads the core subject before the pricing note. No words are wasted, though the phrasing 'overlay near the parcel' is compact to the point of being slightly unclear.

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?

With no annotations, one required parameter, and no parameter explanation, the description is not fully sufficient on its own. The presence of an output schema helps, but the agent still lacks clarity on what value to pass for gnaf_id and when to use this tool instead of other risk-related siblings.

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%, and the description does not explain the required gnaf_id parameter beyond the implicit 'parcel' context. The parameter name is probably recognizable, but the description adds no explicit meaning to help an agent construct a correct call.

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 identifies the resource as a mobile-coverage black-spot overlay near the parcel, which clearly distinguishes it from other risk tools like flood, bushfire, or heritage. It lacks an explicit verb like 'get' or 'return', but the noun phrase is specific enough for an agent to understand what is being described.

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 about when to choose this tool over alternatives such as properties_risks_all, properties_risks_bushfire, or other risk overlays. The pricing note is useful but does not help an agent decide between similar sibling tools.

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