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

With no annotations, the description carries the full burden, and it does disclose the output scope, the included statistics, GeoJSON format, and the 30¢ per-call cost. It does not mention potential limits, data recency, or that the operation is a read, but the low-risk query nature makes the omission less severe.

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?

Two short sentences with no filler. The core output and scope are front-loaded, and the pricing note is the only secondary content. Every word 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 output schema and geojson parameter description already cover return structure and the geometry toggle, so the description does not need to restate them. However, the absence of usage guidance and gnaf_id semantics leaves some selection and invocation details to inference.

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 coverage is only 50%, with geojson fully described in the schema but gnaf_id undocumented. The description never mentions gnaf_id or explains how the property is identified, so it does not compensate for the missing parameter semantics.

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 precisely: mesh-block polygons within 1 km of the property, in GeoJSON, with a defined set of statistics. It is distinguishable from sibling tools like suburbs_shapes_mesh_blocks by its property-centered scope, though it lacks an explicit verb such as 'Returns' or 'Gets'.

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 properties_context_nearby_for_sale, properties_surroundings_parcels, or suburbs_shapes_mesh_blocks. The emphasis on 'within 1 km of the property' implies a property-context use case, but no explicit condition or exclusion is stated.

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