Window Job Submit

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

Annotations already indicate this is not read-only, not idempotent, not destructive, and not open-world. The description adds that submission is asynchronous and returns a queryable request_id, but it does not explain idempotency_key behavior, failure modes when the window host is not confirmed, or interaction with cancellation/status tools.

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 a single compact sentence that front-loads the action, target host, asynchronous behavior, and return handle. Every phrase contributes 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?

For an asynchronous mutation-like submission tool with nested arguments and an output schema, the description covers the core action and return handle but omits parameter semantics and operational preconditions. The output schema reduces the need to explain return values, but the 0% schema coverage leaves important input gaps.

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% for three parameters, so the description must carry the burden. It only implies aprx_path=CURRENT for the nested arguments and mentions request_id as a return value; tool_name, the arguments object, and idempotency_key remain unexplained.

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 action: asynchronously submit a tool invocation to the confirmed CURRENT window host with aprx_path=CURRENT and return a queryable request_id. It is clear what the tool does, though it does not explicitly name sibling alternatives such as window_job_status or sdk_gp_job_submit.

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 phrase '已确认的 CURRENT 窗口宿主' gives an implied prerequisite for use, but there is no explicit guidance on when to prefer this tool over synchronous GP execution or other job submission/status tools. Usage context is only implied.

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