Gp Run Tool

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false and idempotentHint=false. The description adds value beyond these by noting that results are verifiable/structured and that write and path restrictions depend on service capability, which flags potential permission limits. It does not describe what gets written or the parameter-passing behavior, so it is adequate but not rich.

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?

A single compact clause that is front-loaded with the core action. It avoids padding, though it is arguably under-specified rather than maximally efficient.

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?

An output schema exists, so return values need not be explained. However, for a generic GP runner the definition should clarify how tool names and parameters are supplied and how it relates to the specific gp_* siblings; none of that context is present, leaving the definition incomplete for its complexity.

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 neither 'tool_name' nor 'parameters' is documented in schema or description. The description fails to compensate, giving no guidance on naming the target tool or how the arbitrary 'parameters' object should be structured. This is a real gap for a generic dispatcher.

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 verb+resource ('运行工具' / run tool), which tells the agent it executes a generic geoprocessing tool. However, it does not distinguish this generic runner from the large family of specific gp_* siblings (buffer, clip, dissolve, etc.), leaving the agent to infer that this is a by-name dispatcher. The purpose is implied rather than clearly scoped.

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?

There is no guidance on when to use this versus the dozens of named geoprocessing sibling tools. The description never explains that this should be used for arbitrary/unlisted tools while specific siblings cover common operations. No prerequisites or exclusions are given.

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