Sdk Gp Job Cancel

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

Annotations already declare readOnly=false, destructive=false, idempotent=true, and openWorld=false. The description adds that cancellation is requested via an SDK cancellation token and requires a write switch and confirm=true, which are operational preconditions not captured by the annotations. It does not describe asynchronous effects or failure modes, but this is solid given annotation coverage.

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, front-loaded with the action and the key requirements, with no filler content.

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, and annotations cover the safety and idempotency profile. The description supplies the cancellation mechanism and preconditions, though it is sparse on the two required session/job parameters and does not state what happens if the job has already completed.

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%, so the description must compensate. It explains that confirm must be true and that a write switch is needed, but it leaves sdk_session_ref and job_id without added semantics beyond their titles.

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 specific verb (cancel) and resource (asynchronous GP job) and identifies the mechanism (SDK cancellation token). It distinguishes this operation from sibling tools such as arcgis_pro_sdk_gp_job_status and arcgis_pro_sdk_gp_job_submit by the verb, but it does not explicitly name an alternative or scope boundary.

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?

It explicitly states operational prerequisites: write switch must be enabled and confirm=true must be supplied, which tells the agent when the tool can be invoked. It does not state when not to use it or explicitly route to a sibling alternative, but the context is clear.

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