run_advanced_geoprocessing

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

With no annotations, the description bears the full burden of behavioral disclosure. It does communicate two rules: absolute paths must be declared and outputs must be in scratch. However, it omits critical details such as potential side effects (e.g., data modification), permission requirements, confirmation/overwrite semantics (even though confirm and overwrite parameters exist), and whether the operation is read-only or destructive. For a tool that runs arbitrary GP tools, this is a significant gap.

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 concise: two short sentences with no redundancy. It front-loads the core purpose and then adds the key constraint. While it is sparse, it is efficiently structured and avoids filler.

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 complexity of the tool – 7 parameters, nested objects, an output schema, and a sibling 'run_geoprocessing' – the description is notably incomplete. It does not explain how to use the 'tool' parameter, how to construct args/kwargs, what 'confirm' and 'overwrite' control, or how the output schema relates to the returned result. The presence of an output schema reduces the need to explain return values, but the description still fails to cover essential invocation details.

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 coverage is 0% – no parameter descriptions are provided in the schema. The description partially addresses input_paths and output_paths by stating that paths must be declared and outputs must be in scratch, but it does not explain the tool, args, kwargs, confirm, or overwrite parameters. This is insufficient compensation for the lack of schema documentation.

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 states a clear purpose: 'Run an opt-in ArcPy GP tool.' It identifies the resource (ArcPy geoprocessing tool) and the action (run). However, it does not explicitly distinguish from the sibling 'run_geoprocessing', relying on the 'advanced' naming to imply difference. The constraint 'Every absolute path must be declared; outputs must be in scratch' adds specificity about scope but does not define what makes it advanced.

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 offers no guidance on when to use this tool versus the simpler sibling 'run_geoprocessing'. It mentions 'opt-in' but does not clarify what that entails or when it is appropriate. No alternative tools are named, and no conditions are given to help an agent decide between the two geoprocessing tools.

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