save_project

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

No annotations are provided, so the description carries full transparency burden. It merely states 'aprx.save' without detailing behavioral traits such as overwriting behavior, whether it requires an open project, or if it triggers any side effects (e.g., saving unsaved changes). This is insufficient for an agent to understand all implications.

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 extremely concise—one short sentence that immediately states the action and resource. It is front-loaded with the key information and contains no extraneous words, making it efficiently readable.

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 the tool's simplicity (single parameter, no annotations), the description is minimally adequate. However, it omits mention of the return value (an output schema exists but is not referenced) and prerequisites (e.g., the project must be loaded). A slightly richer description would improve completeness.

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?

The only parameter (aprx_path) is described in the schema as 'Absolute .aprx path.' The tool description adds nothing beyond this. Since the schema already provides a clear description, a baseline score of 3 is appropriate; no extra semantic value is contributed by the main 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 clearly states the verb 'Save' and the resource '.aprx project file'. It references the underlying arcpy method 'aprx.save', making the tool's action unambiguous. However, it does not elaborate on the scope (e.g., saves all changes) or differentiate from siblings, which are all distinct tools, so it doesn't quite reach 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?

The description provides no guidance on when to use this tool vs. alternatives or when not to use it. Sibling tools like compact_gdb or rename_dataset are unrelated, but the lack of any context (e.g., 'Use after modifying a project') means the agent must infer usage from the name alone.

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