save_project

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

With no annotations, the description carries the full burden. It discloses the operation (aprx.save), the scope (operates on saved .aprx file), and the return value (saved project path). The behavior is transparent and no contradictions.

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 three sentences: first states the action, second gives usage context, third specifies constraints and return. Every sentence adds value with no redundancy.

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?

For a simple save tool with one parameter and no annotations, the description is fully complete. It explains the operation, when to use, parameter constraints, and return value, covering all needed context.

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 single parameter aprx_path has 0% schema description coverage, but the tool description adds crucial meaning: it must be an absolute path inside a PathGuard allowed root, and operates on saved project files, not live sessions. This compensates well.

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 tool saves an ArcGIS Pro .aprx project using aprx.save, specifying the resource and action. It differentiates from sibling tools by being the only tool that explicitly persists project changes.

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 clear context on when to use the tool: after a sequence of changes when persistence is needed before export or handoff. It implies not to use if no persistence required, though no explicit alternatives are mentioned since none exist.

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