Save Project

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, covering the safety profile. The description adds that write and path restrictions depend on service capabilities and that structured verifiable results are returned, but omits details like overwrite behavior, error conditions, or effects on unsaved state.

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?

Two short sentences with no wasted words and the core action front-loaded. The second sentence is somewhat generic boilerplate, but overall the definition is efficiently sized.

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, and annotations cover safety behavior. However, for a save mutation the description lacks critical operational context such as overwrite semantics, whether it saves the current project or a copy, and the exact meaning of the service-capability caveat.

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% and the description never mentions aprx_path. Though the parameter name is fairly self-explanatory, the description adds no meaning, format, or constraints beyond the bare schema, which is a gap for a required path argument.

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?

States a specific verb and resource ('保存工程' / save project), making the purpose immediately clear. However, it does not differentiate itself from the closely named sibling arcgis_pro_save_project_copy, leaving the agent to infer the distinction from the name alone.

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 guidance on when to use this tool versus alternatives like arcgis_pro_save_project_copy or arcgis_pro_reload_project. Usage is only implied by the tool name; no prerequisites, timing, or exclusions are provided.

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