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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful context beyond that — the enumerated state lifecycle (active, queued, converting, failed, awaiting_upload) and the plan gating — but says nothing about ordering, limits, or what an empty result means.

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?

Front-loads the identity of the resource before the field list, and the sentences are individually informative. The upload/conversion sentence is slightly tangential for a read-only list tool, but it earns its place by preempting a common false expectation that this tool creates layers.

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 does the work of describing return contents (states, geometry, zoom range, URL template), which is what an agent needs to use the results. Missing only edge-case information such as pagination or failure semantics, which is minor for a workspace-scoped list.

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 tool takes zero parameters, so there is nothing to disambiguate and the baseline applies; the description correctly avoids inventing argument details. No further parameter meaning is needed or expected for a parameterless list operation.

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?

States a specific resource — the workspace's hosted data layers served as vector tiles — and enumerates what is returned (name, state, source layers, zoom range, tile URL template). That is clearly distinct from list_maps, list_styles, and list_sprites, though the description never names those siblings to make the distinction explicit.

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?

Gives real context: the output is meant to provide a tile URL template to add to a map, and it explicitly excludes creation by noting that uploading happens in the dashboard (pmtiles, or GeoJSON/CSV converted in background). It also states a plan prerequisite (Studio and above). It stops short of naming which sibling to call when the goal is a map or style rather than a layer.

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