Layout Upsert Element

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

Annotations already declare this is a non-read-only (mutation) but idempotent and non-destructive operation, so the safety profile is covered. The description adds only the element-type scope; it says nothing about how an upsert resolves conflicts with an existing element of the same name, whether untouched properties are preserved, or which parameters are meaningful for which element type.

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; the verb and scope come first and the element enumeration follows. It is efficient, though it is arguably too terse given 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 need not be explained, but for a 22-parameter upsert spanning eight element types with 0% schema coverage the description is far too thin. An agent has no way to know which optional parameters matter for a given element_type or what 'semantic' creation implies.

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% across 22 parameters, so the description carries the full burden and largely fails it: x, y, style, width, height, visible, rotation, font fields, picture_path, table_name, map_name and more get no explanation. Its one real contribution is enumerating the valid element_type values (text, picture, map frame, legend, scale bar, north arrow, grid, table frame), which the schema leaves unconstrained.

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 names a specific verb pair (create or update) and the resource (layout elements), then enumerates the eight element types it handles, making the scope clear against siblings like arcgis_pro_update_layout_text_element (text only) or arcgis_pro_set_layout_element_position. It stops short of explicitly distinguishing itself from those narrower siblings, which is why it is not a 5.

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?

There is no when-to-use guidance and no named alternative. An agent cannot tell from the description whether to call this tool for modifying an existing text element or arcgis_pro_update_layout_text_element, nor when upsert is preferred over the more targeted position/visible setters.

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