Apply Gallery Symbol

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

Annotations already declare this is a non-read-only, non-destructive, idempotent operation, so the safety profile is covered. The description adds the behavioral detail that duplicate symbol names are disambiguated by index, but it does not describe permissions, side effects, or what happens when no symbol matches the wildcard. With annotations carrying the main behavioral burden, a 3 is appropriate.

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 single sentence is front-loaded with the core action and contains no filler. It is compact and direct, though the extreme brevity contributes to gaps in other dimensions rather than representing excessive length.

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?

For a mutation tool with five parameters, zero schema descriptions, and no output schema explanation needed, the one-sentence description is too thin. It omits usage context, most parameter semantics, and behavioral details about the application of the symbol. The presence of an output schema covers return values, but the input-side gaps remain large.

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%, so the description must compensate for five undocumented parameters. It only explains the index parameter, stating it disambiguates duplicate names. It does not explain wildcard, aprx_path, map_name, or layer_name, leaving most parameter meaning to the agent's inference.

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 states a specific action: applying a matching symbol from the project symbol gallery to a SimpleRenderer. It also names the mechanism for resolving duplicate symbol names via index. It does not explicitly differentiate from siblings such as arcgis_pro_set_simple_renderer or arcgis_pro_apply_symbology_from_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?

The description gives no guidance on when to use this tool versus alternatives. It does not mention prerequisites, when the gallery should be used instead of applying symbology from a layer, or any conditions or exclusions. Usage is only implied by the purpose statement.

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