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

Annotations already declare readOnlyHint and openWorldHint=false, so safety is covered. The description goes beyond that by disclosing the exact returned fields and the geometry simplification behavior (~10 m, 5 decimals) — concrete behavioral detail an agent can use to decide whether to request geometry.

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 tight sentences with no filler. The field enumeration is front-loaded, though the sentence opens as a fragment ('The workspace's service zones...') rather than with an explicit verb.

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 output schema, the description substitutes by enumerating return fields in detail. The main gap is the absence of routing guidance relative to zones_for_location, but for a zero-required-parameter read tool it is otherwise complete enough to invoke correctly.

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% and include_geometry has no schema description, but the description compensates by explaining what include_geometry adds and how the GeoJSON is simplified. zone_id is left to the schema's 'Only this zone', which is adequate but thin.

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?

Specific resource and field list: service zones with id, name, colour, active, area, vertex count and record counts. It clearly describes what the tool returns, but does not differentiate from the related sibling zones_for_location or the many other list_* tools.

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 when-to-use, when-not, or alternative guidance. The presence of a sibling zones_for_location raises an obvious route-selection question that the description never addresses.

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