Upsert Chart

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the write and idempotent nature is known. The description adds that it does not perform CIM guess deletion, which is a useful behavioral note beyond annotations, though it is cryptic and does not cover 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?

The single sentence is front-loaded with the core action and resource, and contains no redundant or filler content. It could be slightly more informative without becoming verbose, but it is appropriately concise.

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?

Given 26 parameters with no schema descriptions and an output schema present, the description is far from complete. It covers only the title and chart types, leaving an agent without guidance on most parameters or usage context, so it is insufficient for correct invocation.

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?

With 26 parameters and 0% schema description coverage, the description must compensate but only explains that upsert is by title and lists chart types for the chart_type parameter. All other parameters (x, y, theme, map_name, etc.) are left undocumented in both schema and description.

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 verb (create or update) and resource (chart), and specifies supported chart types (Bar/Line/Scatter/Histogram/Pie) and that upsert is by title. It does not explicitly differentiate from siblings like chart_info or list_charts, but the purpose is clear enough to distinguish it as the only upsert tool for charts.

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 explicit guidance on when to use this tool versus alternatives such as arcgis_pro_chart_info or arcgis_pro_list_charts. The description implies usage for creating or updating charts, but gives no conditions, prerequisites, or exclusions.

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