Add Rasters To Mosaic Dataset

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false. The description adds only that rasters come from 'controlled paths' and that duplicate/pyramid/statistic/thumbnail options can be limited, which mostly echoes parameter categories rather than disclosing mutation impact, permissions, or side effects.

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?

A single front-loaded sentence with no filler. It is appropriately compact, though its extreme brevity for a 14-parameter mutation tool leaves it structurally underdeveloped relative to the tool's complexity.

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?

An output schema exists, so return values are covered. But with 14 parameters, 0% schema description coverage, and no usage guidance, the description is far too thin to support correct invocation of this complex mosaic dataset operation.

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 0% for 14 parameters. The description vaguely mentions duplicate items, pyramids, statistics, and thumbnails, loosely mapping to a few parameters, but provides no types, formats, defaults, allowed values, or meaning for the remaining 10 parameters, failing to compensate for the coverage gap.

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 verb ('把...加入' = add) and resource ('mosaic dataset'), making the core action clear and distinguishing it from remove/create mosaic dataset siblings. However, it does not explicitly differentiate itself from other add-style tools or name any alternative.

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 guidance, no prerequisites, and no alternatives are named. The description just states the operation without helping an agent decide between this and sibling tools like create_mosaic_dataset or remove_rasters_from_mosaic_dataset.

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