run_geoprocessing

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says it 'runs' a tool and explains the input format; it does not disclose whether the operation can modify data, what side effects may occur, whether results are returned, or how errors are handled.

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 compact and well-organized: a one-sentence summary, an Args list, and a single illustrative example. Every sentence contributes useful information, and the core purpose is front-loaded.

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 invocation mechanics are sufficiently documented, and an output schema exists to cover return values. However, with no annotations and no behavioral or usage context, the description is not complete enough for an agent to anticipate side effects or confidently decide between this tool and execute_python.

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 fully compensates by explaining both parameters. It defines 'tool' as a dotted name with multiple examples, and 'params' as a list of positional parameters with a concrete example. This gives an agent enough information to construct valid calls despite the empty schema.

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 starts with a clear action and resource: 'Run any ArcPy geoprocessing tool by its dotted name.' It is specific about the invocation style and gives concrete tool-name examples. However, it does not explicitly distinguish this tool from the sibling execute_python, so it falls short of full sibling differentiation.

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 shows how to invoke the tool with an example, but it gives no guidance on when to use run_geoprocessing versus alternatives such as execute_python. It also does not mention prerequisites, workspace requirements, or any exclusions.

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