run_gp_tool

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

No annotations are provided, so the description must disclose behavioral traits. It mentions returning outputs and messages but does not state whether the tool can modify data, require permissions, or behave destructively. The timeout parameter is mentioned but not its 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 three sentences, front-loaded with the main purpose, and every sentence adds value without 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?

The description covers tool naming and parameter usage, and references describe_gp_tool for signature. However, given the complexity of running arbitrary geoprocessing tools, it lacks cautionary info about side effects, prerequisites, or failure behavior. The output schema exists but is not referenced.

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%, so the description adds essential meaning: explains that tool accepts flat or module names, args for positional parameters, kwargs for named ones. However, it does not describe the timeout_seconds parameter beyond its existence.

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 it runs a geoprocessing tool by name and returns outputs and messages, using specific verb+resource. It distinguishes from sibling describe_gp_tool by advising to use that first for signature uncertainty.

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 advises to use describe_gp_tool if unsure of the signature, and explains naming conventions. It does not explicitly differentiate from sibling arcpy_execute or specify when not to use this tool.

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