set_azuremap_layer_source

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

With no annotations provided, the description carries the full burden. It explains accepted source formats and gives a verification tip, but does not disclose side effects (e.g., whether it overwrites the existing layer source, prerequisites, or failure behavior). This is adequate but leaves gaps in understanding the tool's impact.

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 two sentences long, front-loads the primary action, and uses whitespace to separate the two layer modes. Every sentence provides essential information with no wasted words.

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 tool has 5 required parameters, no annotations, and no output schema, so the description should compensate. It explains the core layer/source logic but omits context about the required reportSessionId (no schema description) and how this tool integrates into the broader workflow. The 'Verify in Desktop' tip is useful but does not fill all gaps.

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 description significantly enriches the schema's parameter definitions. It clarifies what 'reference' means for the layer parameter and provides a concrete tile URL template example for the source parameter. This goes beyond the schema's brief descriptions, adding practical value.

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 clearly states the action: 'Set an azureMap data layer source', with a specific verb and resource. It also distinguishes between the two layer types (reference and tile) with concrete examples, making it unmistakable from sibling 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?

The description provides clear context for when to use each layer type: reference layers for local files/URLs/inline GeoJSON, and tile layers for URL templates. It also advises to 'Verify the render in Desktop', implying a post-action step. However, it does not explicitly mention alternatives or exclusion cases.

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