suburbs_risks_hv_power_linesWhether high-voltage transmission lines cross the suburb, how many, and the highest voltage class (overhead lines only).
| Name | Required | Description | Default |
|---|---|---|---|
| suburb_name | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -{
- "properties": {
- "available": {
- "anyOf": [
- {
- "type": "boolean"
- },
- {
- "type": "null"
- }
- ],
- "description": "`false` on no-data responses. Omitted on success — branch on `data !== null` if you want a single discriminator.",
- "title": "Available"
- },
- "data": {
- "anyOf": [
- {
- "additionalProperties": true,
- "description": "High-voltage electricity transmission lines crossing the suburb.",
- "example": {
- "area_level": "suburb",
- "area_name": "Blacktown",
- "line_count": 6,
- "max_kv": 132,
- "overhead_only": true,
- "present": true
- },
- "properties": {
- "area_level": {
- "const": "suburb",
- "description": "Always 'suburb'.",
- "title": "Area Level",
- "type": "string"
- },
- "area_name": {
- "description": "Canonical ABS SAL suburb name.",
- "title": "Area Name",
- "type": "string"
- },
- "line_count": {
- "description": "Transmission-line features intersecting the suburb boundary.",
- "title": "Line Count",
- "type": "integer"
- },
- "max_kv": {
- "anyOf": [
- {
- "type": "integer"
- },
- {
- "type": "null"
- }
- ],
- "description": "Highest voltage class among the intersecting lines, in kV (null when none intersect or the source carries no voltage class).",
- "title": "Max Kv"
- },
- "overhead_only": {
- "const": true,
- "description": "Underground segments are excluded from the count — only overhead (and unclassified) transmission is counted.",
- "title": "Overhead Only",
- "type": "boolean"
- },
- "present": {
- "description": "True when at least one HV line crosses the suburb.",
- "title": "Present",
- "type": "boolean"
- }
- },
- "required": [
- "area_name",
- "area_level",
- "present",
- "line_count",
- "overhead_only"
- ],
- "title": "SuburbHvPowerLines",
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "description": "The endpoint's payload, or `null` when Microburbs has no value."
- },
- "message": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Human-readable explanation. Omitted on success.",
- "title": "Message"
- },
- "reason": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Machine-readable slug naming the no-data condition (e.g. `no_avm_for_GANSW704074813`). Stable per endpoint. Omitted on success.",
- "title": "Reason"
- }
- },
- "title": "ApiResponse[SuburbHvPowerLines]",
- "type": "object",
- "x-fastmcp-top-level-schema": "ApiResponse_SuburbHvPowerLines_"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this as read-only, idempotent, and non-destructive. The description adds a meaningful limitation: 'overhead lines only,' which clarifies the scope and avoids Agent confusion about underground lines. It also explains the output dimensions (existence, count, highest voltage class), which goes beyond the annotations.
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, tightly worded sentence with no filler. It front-loads the core purpose and packs in the key qualifications (overhead lines, count, voltage class) without 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 simple one-parameter read-only tool, the description covers the essential return values (whether, how many, highest voltage class) and the scope constraint. It does not describe response formatting or error behavior, but given the low complexity and existing annotations, this is sufficient. However, it could have mentioned the expected return type (e.g., object) or behavior for missing suburbs.
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 needs to explain the suburb_name parameter. It never does: no format, no example, no validation, no hint about what qualifies as a suburb. While the parameter name is self-explanatory, there is no concrete guidance on the accepted string format or how to handle invalid inputs.
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 states precisely what the tool returns: whether high-voltage transmission lines cross the suburb, the count, and the highest voltage class, with a clear scope restriction to overhead lines. This distinguishes it from other risk tools like suburbs_risks_flood or suburbs_risks_bushfire, and from the property-level sibling properties_risks_hv_power_line.
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 description gives no guidance on when to use this tool instead of alternatives such as suburbs_risks_all or suburbs_risks_counts. There is no mention of contexts where this tool is preferred or when another risk tool is more appropriate, leaving the agent to infer usage solely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.