Sdk Gp Job Submit

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=false. The description adds 'cancellable' and 'asynchronous', which is useful, but does not explain the side effects of submission, what the whitelist restricts, what the path contract enforces, why it is not idempotent, or what 'confirm' does behaviorally.

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 sentence with no filler. Front-loaded with the action. Appropriately sized for the information it conveys, though it under-delivers on content rather than being over-long.

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 5-parameter mutation tool with 0% schema description coverage, the description omits parameter guidance, confirmation semantics, submission prerequisites, and job tracking (should point to arcgis_pro_sdk_gp_job_status / arcgis_pro_sdk_gp_job_cancel). An output schema exists, so return values needn't be covered, but submission mechanics clearly should be.

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% across 5 parameters, so the description carries the full burden. It mentions none of the parameters explicitly: sdk_session_ref, tool_name, parameters, environments, or confirm. 'Strict whitelist' hints at tool_name constraints but no parameter-level semantics are provided.

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 identifies the action (submit an asynchronous GP job to the SDK) and adds three qualifiers (strict whitelist, path-contract controlled, cancellable). However, it overlaps heavily with siblings like arcgis_pro_gp_run_tool and arcgis_pro_window_job_submit without clarifying how this differs from them.

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?

No explicit guidance on when to use this tool versus arcgis_pro_gp_run_tool, arcgis_pro_window_job_submit, or arcgis_pro_gp_* tools. The 'whitelist' and 'path contract' hints imply constraints but don't tell the agent when to select this tool. The 'confirm' parameter suggests a prerequisite gate that is never explained.

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