xyz_add_layer

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

Provides useful url format requirement and default server info. Without annotations, the description partially fulfills behavioral disclosure, but misses details like idempotency or conflict behavior.

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?

Concise, three-sentence description with front-loaded purpose. Efficiently conveys key information without unnecessary text.

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?

Given 5 parameters, no annotation, and low schema coverage, the description is incomplete. It covers only one parameter's semantics and omits behavioral context for the other parameters.

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?

With 0% schema description coverage, the description only explains the url parameter format. It does not describe crs, zmin, zmax, or layer_name, leaving significant gaps.

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?

Description clearly states it adds an XYZ tile raster layer as a background basemap, distinguishing it from other layer types. However, it could more explicitly contrast with sibling add-layer tools like wms_add_layer.

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?

Describes the typical use case (background basemap) and includes a policy reminder for heavy usage. But lacks explicit when-to-use or when-not-to-use compared to alternative layer-adding tools.

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