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

Annotations indicate readOnlyHint=false and destructiveHint=false, but the description adds no behavioral context beyond the basic action. It does not disclose whether loading replaces existing layers, requires network permissions, or has side effects like duplicate layers if called twice.

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, front-loaded sentence with no filler. Every word contributes to conveying the core purpose and accepted service types.

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 description is minimal and does not elaborate on differences between the four service types or how parameters like layerName and opacity interact. Given 6 parameters and multiple protocols, more guidance would be helpful, though the schema covers parameter descriptions.

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 100%, so the baseline is 3. The description repeats the service types that are already in the schema enum and does not add any new parameter meaning or usage nuance.

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 '加载影像服务图层（WMS/WMTS/XYZ/ArcGIS MapServer）' clearly states the action (load) and resource (imagery service layer), and explicitly lists supported service types, distinguishing it from sibling tools like load3dTiles and loadTerrain.

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 mentioned service types (WMS/WMTS/XYZ/ArcGIS MapServer) provide clear context for when this tool is appropriate, but there is no explicit statement about when not to use it or alternatives. Sibling names imply alternatives, but no exclusion guidance is given.

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