arcgis_symbology

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

No annotations are provided, so the description carries the full burden. It discloses that changes appear immediately in the Pro window, and explains parameter behavior (e.g., 'classes' only for graduated). However, it doesn't mention error handling or permanence of changes, but the main behavioral traits are covered.

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 concise with three sentences: first states purpose, second explains renderer types, third gives an example. No fluff, front-loaded with the core action.

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?

With 7 parameters and no output schema, the description covers the tool's purpose and parameter usage well, including an example. It lacks details on potential errors or prerequisites (e.g., field must exist), but overall it is sufficient for an agent to use the tool correctly.

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 coverage is 100%, but the description adds significant value beyond schema descriptions: it explains the purpose of 'renderer' with examples, clarifies that 'classes' and 'method' apply only to 'graduated', and gives a concrete example. This enhances understanding beyond the parameter names.

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 ('套用渲染器' apply renderer) and the resource ('要素图层' feature layer), with immediate visual feedback. It distinguishes between two renderer types ('graduated' and 'unique'), making the purpose precise and unambiguous.

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 explains when to use each renderer: 'graduated' for numeric fields and 'unique' for categorical fields. While it doesn't explicitly exclude siblings, the sibling tools (e.g., export, query) are clearly different, so usage context is clear.

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