Sdk Edit Save

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

Annotations only cover the safe/read-only/idempotent profile; the description adds two requirements the annotations do not convey – the SDK edit switch must be on and confirm=true is mandatory. That is genuine added behavioral context, though it says nothing about conflict handling or what happens to edits on failure.

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 tight sentence that front-loads the action and follows with the gating requirements. No filler, every clause earns its place.

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?

The mutation's purpose and gating requirements are conveyed, and an output schema exists so return values need not be described. But two required parameters remain opaque and there is no note on expected_edit_generation's role as a conflict guard, leaving the definition only minimally sufficient.

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 carries the full burden, yet it only addresses one of three parameters (confirm=true). The required 'sdk_session_ref' and 'expected_edit_generation' (apparently a concurrency/optimistic-lock token) are left completely unexplained.

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?

Names a specific verb (保存/save) and resource ('当前工程中的待提交数据编辑' – pending edits in the current project), which clearly identifies the operation and implicitly contrasts with the discard/undo/redo siblings. It does not explicitly name those alternatives, so it stops short of 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?

Gives concrete preconditions ('需要 SDK 编辑开关和 confirm=true'), which is real usage guidance. However it never states when to prefer saving over arcgis_pro_sdk_edit_discard, edit_apply, or other commit paths, so the when-vs-alternative guidance is only implied.

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